Comments on How To Configure SSH Keys Authentication With PuTTY And Linux Server In 5 Quick Steps

Hi folks,

I wrote an article about PKA as well

http://sunoano.name/ws/public_xhtml/ssh.html#public_key_authentication

 Maybe someone might find it useful ...

http://www.ssh-key-authentication.com/

 i wrote anything you need to know and more at that site

plus : you get an automatic script.

enjoy

Hi there ... 

Hints:

Your howto advices people to use scp to transfer the public key to the remote machine. This often causes permission problems. The prefered way is to use ssh-copy-id as shown here

http://sunoano.name//ws/public_xhtml/ssh.html#transferring_the_public_key_to_the_remote_machine

Also, just to stress the fact again, a keypair should always be protected by a passphrase i.e. "leaving empty for no password" should not be done:

http://sunoano.name//ws/public_xhtml/ssh.html#why_does_public_key_authentication_benefit_me

Monkeysphere:

Personally, I am now using Monkeysphere on top of PKA all the time now because it also solves the problem how to authenticate servers and users:

http://sunoano.name//ws/public_xhtml/ssh.html#monkeysphere

perfect article. Works perfect and steps are really explained properly. Only thing is I am using ubuntu so at 3rd step I used sudo su -l autotimesheet command instead of su autotimesheet

Thanks a lot for such a nice article.

This one worked for CentOS http://yesterdayseggs.com/quick-guide-automatically-log-in-to-an-ssh-session-without-a-password/

I believe you didn't set the owner right.

chown -R autotimesheet. /home/autotimesheet/.ssh

If the folder and file were created by the intended user, then no need to change owner permissions. If however, the files and folder were created by another user such as the root, then you would have to change the owner permissions. In this example, it was not necessary. I hope that helps.

The authorized_keys2 file has been deprecated since the OpenSSH 3.0 release (2001).

See

http://marc.info/?l=openssh-unix-dev&m=100508718416162&w=2

You seem to be correct, this didn't work for me using 'authorized_keys2', but worked like a charm using simply 'authorized_keys' as the file name. Using CentOS7.

Thank you very much for the nice introduction :-) I liked it a lot and I am glad to not retype my password every time I connect to my server

Should the == (with a space after) be included at the end of the key?

A noob question... I am using WinSCP to connect to my server via SSH. I went to Settings -> SSH -> Authentication and provided the path to the ppk file. Still WinSCP won't let me sign in without a password.Can anyone tell me, what else I need to do in WinSCP for this to work?

Did you add a passphrase when you created the keys? You don't have to.

What about if you don't have root/su access?   In big companies, they might not allow this.

Many thanks for the simple How-To - works perfectly on my home setup.

Finally someone that explained it for home connecting to server! Saved my day!

Hi,

I am able to login to the CSPC console using vm console but unable to access console using ssh/putty?

please help.

thanks,

Manshaw

Thaink you for the details of the tutorial !!!

Thank you for sharing this important information.

Thanks so much from this!

I am getting Putty FATAL ERROR: No supported authentication methods available (server sent: publickey) on following all these steps.

Can somebody help? 

Check that you are using the latest putty version.

Same here -- thanks.

Remarks :

Take care, it's not :

adduser autotimesheet --disabled-password

but

adduser --disabled-password autotimesheet

:)

ssh authentication browse bar not seen on my laptop what is the problem