Comments on How To Set Up SSH With Public-Key Authentication On Debian Etch

here are a couple of additional tips:

you don't need to create the .ssh direrectory yourself, ssh-keygen will do that for you if its unable to find it. 

And to copy keys: 

ssh-copy-id -i .ssh/id_rsa [email protected]


You can also use ssh-copy-id to copy over your key to the remote host as well.  If no .ssh  directory or authorized_keys file exists, it creates them or if they do, it appends the key to the end of the authorized key file.

Hi,

Thanks for replying.

I created the ".ssh" directory, because later we modify the privileges of the directory. You're right we could do that we generate the key and then we chmod the ".ssh" dir, but I think it's simplier...

By the way, I didn't know about ssh-copy-id command; it's really a great tool, thanks for notifying me about that.

Shouldn't it be like...?:

ssh-copy-id -i .ssh/id_rsa.pub [email protected]

I'll guess you want to keep your private key for yourself.

Thanks for this HOWTO manual - it`s very useful.

I just followed it almost verbatim (I use aptitude instead of apt-get) on Debian/Squeeze and it worked perfectly. Presumably that means it also works on Lenny.

 Thanks for the howto!

I cannot understand the necessity of this command:

   mv id_rsa.pub ~/.ssh

Why do you move the public key into ~/.ssh on the remote server? It exists already in the file ~/.ssh/authoreized_keys

HelloI am having trouble using the system. When I log on I should have ubuntu and we have to put public key so instead of passwordI want to know how to log on change where user name Root and speak the mystery of normal is not so public key

Moving this file isn't necessary. I having copies of every  remote machines public keys to identify keys in authorized_keys