From owner-freebsd-newbies@FreeBSD.ORG Mon Jan 17 21:24:55 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 34D7616A4CE for ; Mon, 17 Jan 2005 21:24:55 +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 111E043D1D for ; Mon, 17 Jan 2005 21:24:55 +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); Mon, 17 Jan 2005 13:24:54 -0800 Message-ID: <41EC2CFA.2020009@finnovative.net> Date: Mon, 17 Jan 2005 13:24:10 -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> <41EC2880.3070905@wingfoot.org> In-Reply-To: <41EC2880.3070905@wingfoot.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Jan 2005 21:24:54.0975 (UTC) FILETIME=[FCEE1CF0:01C4FCDA] 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: Mon, 17 Jan 2005 21:24:55 -0000 Glenn Sieb wrote: > Joaquin Menchaca said the following on 1/17/2005 4:01 PM: > >> Just some questions about telnet. I just installed FreeBSD. I want >> to setup so that I can telnet into it and do some work on it (as it'll >> be the server for the house) > > > Telnet is a highly insecure solution. It has generally been replaced > with ssh (Secure SHell). Hi. Then how can I get SSH working? I can use this. My target client platform now is Mac OS X, so interoperability between FreeBSD and Mac OS X is smoother. 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. Windows can secure insecure applications through through IPSec. This might be similar to kerberorized tools in Solaris and stunnel for others. Eventionally, I want to play with them all, feret out which ones are painful, which ones are the best, and what ones work between platforms (linux vs. solaris vs. freebsd vs macos vs windows). :-> One complaint I've heard with SSH though is that bad stuff can still get through a firewall, such as a downloading of a known trojan/virus, can cannot get stripped out. Whereas, SSL could potentially get stipped out. Anyways, I'm far from that point yet. I just need some sort of access into the box. I'm behind a firewall. -- joaquin