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?
reshared this
Whovian NineThreeSixNine
•Jonathan Lamothe
Whovian NineThreeSixNine
•Nire Bryce
•Jonathan Lamothe
Nire Bryce
•Jonathan Lamothe
Okay, here's where it gets weird:
I installed PuTTY on my home machine using Wine so I could test it. It worked flawlessly.
Jonathan Lamothe
Jonathan Lamothe
It turns out I'm an idiot.
I have a bunch of machines on my LAN that all port forward out to the same VPS on different ports. I was mistaken about the port number (and therefore the host) and his account wasn't actually there. This is why it didn't bother with the key, and is also why I could connect as I have an account on all of them.
Hobson Lane
•social elephant in the room
•grep -i pubkey /etc/ssh/sshd_config
PubkeyAuthentication yes
randygalbraith
•