From owner-freebsd-isp Wed May 13 04:16:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08296 for freebsd-isp-outgoing; Wed, 13 May 1998 04:16:06 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08187 for ; Wed, 13 May 1998 04:16:01 -0700 (PDT) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id VAA11343; Wed, 13 May 1998 21:15:48 +1000 (EST) Date: Wed, 13 May 1998 21:15:47 +1000 (EST) From: "Daniel O'Callaghan" To: Karl Pielorz cc: isp@FreeBSD.ORG Subject: Re: Rhosts question... In-Reply-To: <355971B9.23080379@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 13 May 1998, Karl Pielorz wrote: > I've just read one article though that was refering to the way implementing > .rhosts can stop you from having to send the root password accross the > network, and therefore is a more 'secure' way of constantly logging into > machines as root etc. > > Has anyone got any comments on this? > > I guess I really should look at setting up SSH if it's bothering me that > much... ;-) r commands do reduce password transmission in clear text, but often don't eliminate it. They are also dependent on accurate DNS. SSH and friends are much more secure, especially if used with RSA public key authentication. Once you get the hang of it, SSH is also easy to install and use. Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message