From owner-freebsd-security Fri Jan 7 15:10:49 2000 Delivered-To: freebsd-security@freebsd.org Received: from naiad.eclipse.net.uk (naiad.eclipse.net.uk [195.188.32.29]) by hub.freebsd.org (Postfix) with ESMTP id 7327214BDA for ; Fri, 7 Jan 2000 15:10:47 -0800 (PST) (envelope-from sh@eclipse.net.uk) Received: by naiad.eclipse.net.uk (Postfix, from userid 65534) id DC2931393D; Fri, 07 Jan 2000 23:10:43 +0000 (GMT) From: Stuart Henderson To: Brett Glass Reply-To: Stuart Henderson Cc: Matthew Dillon , Christian Weisgerber , freebsd-security@FreeBSD.ORG References: <854v9q$1gf9$1@bigeye.rhein-neckar.de> <4.2.2.20000107155733.01d32b40@localhost> In-Reply-To: <4.2.2.20000107155733.01d32b40@localhost> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: IMP 2.0.10-cvs X-Complaints-To: abuse@eclipse.net.uk X-Trace: webmail.octarine.org/212.104.138.174 Subject: Re: dump over ssh Message-Id: <20000107231043.DC2931393D@naiad.eclipse.net.uk> Date: Fri, 07 Jan 2000 23:10:43 +0000 (GMT) Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Brett Glass : > Can you do any or all of these things from a script? As I recall, > ssh requires "live" entry of the password from the keyboard (though > I haven't tried it lately). There is an rhosts-like mechanism in ssh (shosts), alternatively you can leave the passphrase blank when you run ssh-keygen and then use authorized_keys files, or you can use an authentication server. More information in ssh(1). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message