That's true. ssh-agent is another way of doing it if the key is passwordless,
however I've never played with it. Guess it's time to start :)
ml
On Sunday 20 July 2003 03:19 pm, Mark A. Hershberger wrote:
> Manuel Lora <vanguardist@cox.net> writes:
> > Asuming it's for ssh2, you need to create a pair of keys, using
> > 'ssh-keygen -t rsa' then you upload/move/copy/rename the public key
> > (from ~/.ssh/id_rsa.pub) to the remote server and place it in
> > ~/.ssh/authorized_keys2 (either copy or append, if you have more
> > than one there already), and that should be it.
>
> If you are confident that no one will gain possession of your keypair
> so you feel safe without using a passphrase for your keypair (and,
> further, not limiting the capabilities of the keypair) then this will
> work.
>
> If you want to protect your keypair with a passphrase (a wise
> decision) or limit it to backing up your files, then you've got more
> work to do involving ssh-agent (for interactive logins) or limiting
> what actions the keypair can perform on the remote host (by adding a
> "command=''" to the authorized_keys file).
>
> > If it's not working, check sshd_config to allow for public keys (default
> > should be yes, iirc).
>
> Permissions on the various files under ~/.ssh also cause problems.
>
> Mark.
> ___________________
> Nolug mailing list
> nolug@nolug.org
___________________
Nolug mailing list
nolug@nolug.org
Received on 07/20/03
This archive was generated by hypermail 2.2.0 : 12/19/08 EST