Re: [tlug] Dealing with a second SSH key

[Christian Horn <chorn@example.com>]

On Sat, Oct 11, 2008 at 02:25:25PM +0900, Charles Muller wrote:
> 
> chuck@example.com:~$ ssh -vv -i /home/chuck/.ssh/id_dsa_sat acmuller@example.com
> [...]
> Which yields:
> 
>      chuck@example.com:~$ ssh -vv -i /home/chuck/.ssh/id_dsa_sat acmuller@example.com
>      [...]
>      debug1: Next authentication method: publickey
>      debug1: Offering public key: /home/chuck/.ssh/id_dsa_sat
>      debug2: we sent a publickey packet, wait for reply
>      debug1: Server accepts key: pkalg ssh-dss blen 433
>      debug2: input_userauth_pk_ok: fp 4a:7c:e0:49:c2:ab:57:6c:d6:41:6e:f3:da:35:f3:02
>      debug1: PEM_read_PrivateKey failed
>      debug1: read PEM private key done: type <unknown>
>      Enter passphrase for key '/home/chuck/.ssh/id_dsa_sat': {entered}
>      debug1: read PEM private key done: type DSA
>      debug1: Authentication succeeded (publickey).
>      [...]

Congrats, you used pubkey-auth now.
You should also be able to use rsync over this.
Now you can go to your other topics:
- generate and use a keypair without passphrase
- restrict usage of the keypair to only rsync-usage


Christian