Date: Mon, 26 Feb 2001 20:00:05 -0800 (PST) From: Dennis Glatting <dennis.glatting@software-munitions.com> To: Ernst de Haan <ernst@jollem.com> Cc: Steve Price <steve@havk.org>, <ports@FreeBSD.ORG> Subject: Re: Changing rsync to use SSH rather than RSH by default Message-ID: <Pine.BSF.4.31.0102261957120.23250-100000@btw.plaintalk.bellevue.wa.us> In-Reply-To: <20010227033214.A4431@c187104187.telekabel.chello.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Feb 2001, Ernst de Haan wrote: > > The POLA-purists would probably say something like make it > > configurable via an environment variable like RSYNC_RSH and > > have it default to /usr/bin/rsh if not overridden in the > > user's environment. Also many people are probably using > > rsync on internal networks and don't need the security more > > than they need the speed of transfers. > > For what it's worth: We use ssh even on the internal network, so that > if one box is compromised, they won't be able to sniff out any > passwords. > > Another $ 0.02, which makes $ 0.04 ! ;) > On two networks I dump over SSH. One network is a Frame and the other Ethernet. In each case the limiting factor isn't the crypto but the network and client systems. "Internal network" can mean anything. The Frame network, for example, though geographically dispersed is considered by the company to be an internal network. $0.06. > -- > Ernst > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-ports" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.31.0102261957120.23250-100000>