From owner-freebsd-security Fri Jan 7 16:43: 9 2000 Delivered-To: freebsd-security@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id F20F21593D for ; Fri, 7 Jan 2000 16:42:41 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id BAA24560 for freebsd-security@freebsd.org; Sat, 8 Jan 2000 01:42:40 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id AAA71568 for freebsd-security@freebsd.org; Sat, 8 Jan 2000 00:46:08 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: dump over ssh Date: 8 Jan 2000 00:46:08 +0100 Message-ID: <855ts0$25s2$1@bigeye.rhein-neckar.de> References: <854v9q$1gf9$1@bigeye.rhein-neckar.de> <4.2.2.20000107155733.01d32b40@localhost> To: freebsd-security@freebsd.org Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brett Glass wrote: > Can you do any or all of these things from a script? Of course. Note that the idea (and the main part of the implementation) for "dump -P" is reused from rdist. > As I recall, ssh requires "live" entry of the password from the > keyboard (though I haven't tried it lately). ssh supports several types of authentication. For scripts, you'd probably set up either rhosts-RSA authentication (my personal favorite) or RSA authentication with a keypair without passphrase. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message