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... Message-ID: <20020801143402.GE31051@hal9000.halplant.com> In-Reply-To: <375F68784081D511908A00508BE3BB1701EF1D61@phsexch22.mgh.harvard.edu> References: <375F68784081D511908A00508BE3BB1701EF1D61@phsexch22.mgh.harvard.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Even if this involves a user with another protected key pair, don't forget you can add any number of public keys to authorized_keys and can invoke ssh pointing to a different private key. Exactly how you implement the process will depend on your trust model. Make sure the host key exchange has already happened. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@halplant.com | | "They that can give up essential liberty to obtain a little temporary | | safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 | 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?20020801143402.GE31051>