Date: Fri, 2 Aug 2002 12:51:49 +0200 From: Roman Neuhauser <neuhauser@bellavista.cz> To: Andrew J Caines <A.J.Caines@halplant.com> Cc: "Morse, Richard E." <REMORSE@PARTNERS.ORG>, FreeBSD Questions <FreeBSD-Questions@FreeBSD.org> Subject: Re: Question about ssh setup... Message-ID: <20020802105149.GB47310@freepuppy.bellavista.cz> In-Reply-To: <20020801143402.GE31051@hal9000.halplant.com> References: <375F68784081D511908A00508BE3BB1701EF1D61@phsexch22.mgh.harvard.edu> <20020801143402.GE31051@hal9000.halplant.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Thu, 1 Aug 2002 10:34:02 -0400
> From: Andrew J Caines <A.J.Caines@halplant.com>
> To: "Morse, Richard E." <REMORSE@PARTNERS.ORG>
> Cc: FreeBSD Questions <FreeBSD-Questions@FreeBSD.org>
> Subject: Re: Question about ssh setup...
>
> Richard,
>
> > Hi! I have a problem -- I have a user who wants to be able to
> > connect to my server via a script, get a directory listing, then use
> > scp to copy some files off. The problem is that ssh (which is the
> > only way to connect) doesn't allow you to pass the password to it as
> > a parameter
>
> The canonical solution to this problem is the have the client generate a
> key pair with a null passphrase, then use this key pair for the automated
> connections.
read why this is a bad thing:
http://www.snailbook.com/faq/no-passphrase.auto.html
--
FreeBSD 4.6-STABLE
12:51PM up 2 days, 20:27, 7 users, load averages: 0.10, 0.06, 0.07
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020802105149.GB47310>