From owner-freebsd-security Wed Nov 28 2: 9:43 2001 Delivered-To: freebsd-security@freebsd.org Received: from shikima.mine.nu (pc1-card4-0-cust77.cdf.cable.ntl.com [62.252.49.77]) by hub.freebsd.org (Postfix) with ESMTP id 6594737B416 for ; Wed, 28 Nov 2001 02:09:39 -0800 (PST) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 1691g0-0006jd-00; Wed, 28 Nov 2001 10:10:48 +0000 Date: Wed, 28 Nov 2001 10:10:48 +0000 From: Rasputin To: "Stephen T. Shipley" Cc: security@freebsd.org Subject: Re: crypted remote backup Message-ID: <20011128101048.A25860@shikima.mine.nu> Reply-To: Rasputin References: <200111270147.fAR1lDk16602@e-shipley.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111270147.fAR1lDk16602@e-shipley.com>; from steve@e-shipley.com on Mon, Nov 26, 2001 at 08:47:13PM -0500 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Stephen T. Shipley [011127 03:57]: > Configure rsync.conf on source server (with 40g file) and run as a daemon. Provide a net name like "www" for alias to path. > And possibly run from one of the /etc/periodic/daily scripts like this (on destination box). > > /usr/local/bin/rsync -e /usr/bin/ssh -avz ::www \ I think (though could be wrong) that the double colon here ^^ will cause rsync to use rsh as a transport, despite the fact that you specified ssh as an *available* transport with '-e ssh' earlier. And while we're on the subject, what's the safest way of doing this as root (to preserve permissions, and have access to a whole fs tree; I'm not too bothered about crypto at the destination directory) Cheers. > /usr/local/www/data/home_something_destination && rc=0||rc=3 -- Love and scandal are the best sweeteners of tea. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message