The trick here is to understand which side is the client and which is the server.
Pretty simple in concept, but the reality is a little different.
You copy the public key of the client user to the server user's .ssh directory in the authorised keys.
The server user only needs a .ssh directory
http://linuxproblem.org/art_9.html
There is also this guide
http://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
There is also this one
http://serverfault.com/questions/398/why-wont-automatic-login-through-ssh-with-authorized-keys-work
And this seems to be the real fix...
Pretty simple in concept, but the reality is a little different.
You copy the public key of the client user to the server user's .ssh directory in the authorised keys.
The server user only needs a .ssh directory
http://linuxproblem.org/art_9.html
There is also this guide
http://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
There is also this one
http://serverfault.com/questions/398/why-wont-automatic-login-through-ssh-with-authorized-keys-work
And this seems to be the real fix...
chmod 0600 ~/.ssh/authorized_keys
Comments
Post a Comment