From owner-freebsd-isp Mon Nov 25 17:10:08 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24731 for isp-outgoing; Mon, 25 Nov 1996 17:10:08 -0800 (PST) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA24681 for ; Mon, 25 Nov 1996 17:09:23 -0800 (PST) Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.8.3/8.8.3) with SMTP id UAA05324; Mon, 25 Nov 1996 20:09:06 -0500 (EST) Date: Mon, 25 Nov 1996 20:05:55 -0500 () From: Bradley Dunn Reply-To: Bradley Dunn To: Matt of the Long Red Hair cc: freebsd-isp@freebsd.org Subject: Re: Stupid question no 10101 In-Reply-To: Message-ID: X-X-Sender: bradley@harborcom.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 25 Nov 1996, Matt of the Long Red Hair wrote: > On Wed, 20 Nov 1996, John Capo wrote: > > > If your wire is not secure and you are not filtering at a router > > then copying the password file via an encrypted link is your only > > option. > > A good way to do this is with ssh, a replacement for telnet,rlogin,rsh, etc. > which encrypts all connections. You could scp (secure rcp) your password > files from machine to machine. > > ssh is available as a FreeBSD port, BTW. Check your local mirror. Careful there. If you are in the US or Canada and you are using ssh in a commercial application, you must either have a license with RSA or buy a product that does. (such as F-secure http://www.datafellows.com/f-secure/) -BD