[SOLVED] Private/Public Keys and ssh-add.

[cibonato]

Hello... first of all let me explain the situation: I work on two different places and in each of them I have a computer, sometimes I work from home (using my home computer). SSH connections between these 3 computers are very very common and to make work easy I thought of using key authentication. I read some man pages (ssh, ssh-keygen, ssh-add) and created a kind of procedure to follow.

It's what I'm doing:

1) on the client I run ssh-keygen to create the key pairs.

2) copy the public key to the server and rename it to authorized_keys; this file is saved in ~/.ssh.

3) on the client I make a link called identity pointing to the public key.

4) so I run ssh-add on the client and type the passphrase used to create the key pairs.

After all these steps I try to make a connection between any of these computers. At the first time I have to type the passphrase and from the second on it's not necessary.

So here is where the problems arise. If I turn any of these computers off I have to type the passphrase again all the times I try to make a connection between them. To avoid this I run ssh-add again on the client.

Are there a way to stop this definitely? The idea is to use SSH passwordless, but if I have to type the passphrase all the times it's quite the same.

Thank you.
_________________
64 Bits, good good!

[JeliJami]

you can always generate a keypair without passphrase

less secure, but it works
_________________
Unanswered Post Initiative | Search | FAQ
Former username: davjel

[cibonato]

The solution was to create the key pair without passphrase. Using ssh-keygen -p one can chage the passphrase of a given private key (the command will prompt for the old passphrase), this way I could re-use my keys.

Done!

Thank you.
_________________
64 Bits, good good!