Skip to main content

Jeff MacKinnon reshared this.

This is extremely frustrating.

I host a piece of software on my server for my father. He connects to it via #SSH (using #PuTTY ). He just got a new computer, and wanted me to set it up so that he could connect, just like I did with his previous computer. No problem right?

I show up, generate the key, and authorize it on the server, but for whatever reason PuTTY refuses to acknowledge the existence of this key. I know it's not even trying, because it doesn't even ask for the passphrase to decrypt it.

Has something changed in the latest version of PuTTY that I just don't know about? Do I need to do something the enable public key authentication beyond simply specifying the path to the key?


grep -i pubkey /etc/ssh/sshd_config

PubkeyAuthentication yes

Oh Glad you figured it out. Your initial thoughts and frustrations seems pretty normal. What won the day was your persistent to search several paths -- run PuTTY via Wine -- goodness. Hope your dad was pleased. Cheers, -Randy

Caelyn McAulay reshared this.

Hey lazy web, is there something I can put in my ~/.ssh directory to tell sshd that I don't want to allow password-authenticated connections? I'm not the admin on this machine, so I can't touch the /etc/ssh directory.
#linux #unix #ssh #AskFedi
If you have working public key login, you could probably just ask the admin to disable your password altogether on that system.
@Andrew Pam I could probably have that done at SDF, but I doubt I'll get that level of service from

This website uses cookies. If you continue browsing this website, you agree to the usage of cookies.