From owner-freebsd-newbies@FreeBSD.ORG Wed Oct 6 12:39:37 2004 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 DEEA416A4CE for ; Wed, 6 Oct 2004 12:39:37 +0000 (GMT) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6100443D41 for ; Wed, 6 Oct 2004 12:39:37 +0000 (GMT) (envelope-from metaridley@mchsi.com) Received: from kaworu.dave.cedar-falls.ia.us (12-219-24-19.client.mchsi.com[12.219.24.19]) by sccmmhc91.asp.att.net (sccmmhc91) with SMTP id <20041006123935m9100cdssme>; Wed, 6 Oct 2004 12:39:36 +0000 Date: Wed, 6 Oct 2004 07:38:29 -0500 From: Dave Vollenweider To: freebsd-newbies@freebsd.org Message-Id: <20041006073829.1b5d7b98.metaridley@mchsi.com> In-Reply-To: References: <200410042313.29422.buebo@buebo.de> <6e01203b04100508235492090f@mail.gmail.com> X-Mailer: Sylpheed version 0.9.12-gtk2-20040622 (GTK+ 2.4.9; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: network question 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: Wed, 06 Oct 2004 12:39:38 -0000 On Wed, 6 Oct 2004 11:30:45 +0200 (CEST) Wojciech Puchar wrote: > > > > But really, really think twice before running telnet. Most likely you > > why? > > anyway i prefer rsh/rlogin/rexec > All the programs you've mentioned have a major flaw: they send everything out unencrypted, which means that if someone's sniffing your network connection, which is a lot like someone tapping your phone, they can know everything you're doing. They can even get your passwords this way, including the all-important root password. This is why such programs are considered to be dangerous to run. ssh, on the other hand, encrypts all communication, so anyone sniffing your network would need the public and private keys to decrypt the connection and see what's going on. ssh can do everything that telnet, rsh, rlogin, and rexec can do, plus a whole lot more. Ever wanted to log in remotely to your computer, run an X program off it and have it display on the computer you're currently at? You can do that with ssh without touching X itself at all. Ever wanted to access one of your computers behind your firewall without compromising the firewall's security? With ssh's TCP port forwarding, you can do that too, again with no special setup of anything else. Oh, and if you're on a slow connection, you can compress the ssh session with the -C switch. Hopefully these reasons are compelling enough for you. - Dave V.