Re: [tlug] Dealing with a second SSH key

[Al Hoang <hoanga@example.com>]

Hello,

On Fri, Oct 10, 2008 at 05:44:29PM +0900, Charles Muller wrote:
> A few years ago I succeeded in successfully creating my first ssh keypair, and haven't had to touch it since. But I now want to rsync to a second server (at a completely different domain), and I'm confused about how I'm 
> supposed to handle the two together. If I do
> 
>   ssh-keygen -t dsa
> 
> I am threatened with overwriting my original keypair. But it also seems that I can't simply copy the keypair on my first remote server over to my second remote server (or perhaps I can, and I am doing something wrong with 
> permissions?). I am an absolute beginner at this.
> 
> I can find plenty of ssh keygen howtos and so forth, but I can't seem to find anything that explicitly tells how to deal with a key for a second remote server.
> 
> Any help would be much appreciated.

I'm not a ssh master but here is how I understand you situation...

You generated the first keypair on machine A.  So now you have A_priv and A_pub on
machine A.  You wanted to login to machine B.  So you copied the contents of
A_pub into the authorized_keys file on machine B and are able to login to
machine B with generated ssh keypair.

You now have a machine C that you want to rsync from machine A.  In this case it's quite
easy.  You login to machine C and copy the contents of A_pub into $HOME/.ssh/authorized_keys.
Now you should be able to ssh (and rsync) into machine C from machine A using the keypair.

If the situation is you want to rsync from machine B to machine C.  Generate a new
keypair on machine B then copy the contents of B_pub to machine C.

If I'm incorrect in these assumptions please feel free to point me in the right direction
Alain