From owner-freebsd-isp Mon Nov 25 08:18:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03456 for isp-outgoing; Mon, 25 Nov 1996 08:18:53 -0800 (PST) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03411 for ; Mon, 25 Nov 1996 08:18:46 -0800 (PST) Received: from crunch.io.org (crunch.io.org [198.133.36.156]) by post.io.org (8.8.3/8.7.3) with SMTP id LAA00549 for ; Mon, 25 Nov 1996 11:18:44 -0500 (EST) Date: Mon, 25 Nov 1996 11:18:44 -0500 (EST) From: Matt of the Long Red Hair Reply-To: Matt of the Long Red Hair To: freebsd-isp@freebsd.org Subject: Re: Stupid question no 10101 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. ----------------------------------------------------------------------------- Matthew Pounsett (MP1229) Internet Canada/Internex Online mattp@ican.net / mattp@io.org "In some small towns there is a rule that consultants can't serve as volunteer firemen. The fear is that they'd drive around setting fire to the town." -- Scott Adams