From owner-freebsd-newbies@FreeBSD.ORG Tue Jan 18 09:20:33 2005 Return-Path: Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B741816A4CE for ; Tue, 18 Jan 2005 09:20:33 +0000 (GMT) Received: from mail.finnovative.net (h204-247-59-114.ncal.verio.net [204.247.59.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8283343D4C for ; Tue, 18 Jan 2005 09:20:33 +0000 (GMT) (envelope-from linuxuser@finnovative.net) Received: from [192.168.1.121] ([204.247.59.114]) by mail.finnovative.net over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Jan 2005 01:20:33 -0800 Message-ID: <41ECD4B4.1080106@finnovative.net> Date: Tue, 18 Jan 2005 01:19:48 -0800 From: Joaquin Menchaca User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-newbies@freebsd.org References: <41EC2790.4090500@finnovative.net> <41EC2CFA.2020009@finnovative.net> <200501171439.41285.krinklyfig@spymac.com> <200501171448.30670.krinklyfig@spymac.com> In-Reply-To: <200501171448.30670.krinklyfig@spymac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Jan 2005 09:20:33.0425 (UTC) FILETIME=[F63DA010:01C4FD3E] Subject: Re: HELP: how to enable telnet? X-BeenThere: freebsd-newbies@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Gathering place for new users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 09:20:33 -0000 Joshua Tinnin wrote: > On Monday 17 January 2005 02:39 pm, Joshua Tinnin > wrote: > ... > >>>However, later I want to use Windows XP/2K3. They have decent ssh >>>client support through tools like putty, but I don't know any good >>>sshd solution on Windows. >> >>I don't know if installing a new OS is an option, but any home >>Windows OS pre-2000 is not secure in the first place (i.e., ME, 98, >>95). I would not use any of them if security is a consideration. >> >>BTW, PuTTY works very well, as does installing Cygwin so you can use >>its tools (though that is a bit overkill, maybe). > > > Wait, I'm sorry, I think I misunderstood you. If you want to run a > secure daemon on Windows instead of on *nix, I'm not sure, actually. > You might be able to do this with Cygwin, but I've only used it to > login to sshd on a *nix machine. > > - jt Oh. At home I have 11 computers: 2 sparcs, 2 macs, 8 pcs (mix of PIVs, AMDs, and C3s). They run *nix OSes (SuSE, Fedora, FreeBSD, Solaris, Mac OS X, Tenon) and of course Winows XP/2K3. I don't bother with older OSes, except for experimentation, e.g. learning how older OSes are better supported by UNIX than Windows for both performance and security. Between computers, I want to have interoperability between them (print, file share, X, remoting, rtools/telnet/ftp). For insecure solutions, I was interesting in playing with SSL, SSH, Kerberos, and IPSec. Also, looking into secure single sign-on facility. However, I am far from getting the experiments off the ground. I am just barely above getting the darn things to work, with drivers, wi-fi, bluetooth, etc. Many companies still uncooperative with open source communities, a matter I hope to help proactively. In the mean time, I'll get a handle on SSH facilities (as well as getting hardware to work). Oh, lastly, Cygwin is cool. I'm interested in both cygwin and non-cygwin (mingw) solutions for both client/server. I tried all the client tools, both putty and ssh, both work well. Never knew that sshd was working so well. :-> Wish there was a way though to redirect the Windows desktop as a X client ;-> -- joaquin