Re:PuTTY vulnerability vuln-p521-bias
by orev on Monday April 15, 2024 @04:23PM
(#40045134)
You should be using pageant to store the secret ssh keys, and you only need to unlock the key on reboot/first use.
[ Parent
| on HN ]
Re:PuTTY vulnerability vuln-p521-bias
by spacemanspiff01 on Monday April 15, 2024 @06:15PM
(#40046315)
Windows has a built in ssh-agent included with openssh, no need for pagent anymore.
Ssh agent will manage your ssh keys through windows registry windows login process.
Also if you use wsl, you can access your ssh keys in wsl from the windows ssh-agent via npiperelay
Re:PuTTY vulnerability vuln-p521-bias
by yau8edq12i on Tuesday April 16, 2024 @09:02AM
(#40051369)
You don't even need a relay to use the windows SSH agent from wsl. Simply use ssh.exe instead of /bin/ssh. I've been doing that for a while (I make a symlink in a folder from my PATH that gets picked up before /bin) and haven't encountered any issues so far.
Re:PuTTY vulnerability vuln-p521-bias
by spacemanspiff01 on Friday April 19, 2024 @08:34AM
(#40086023)
Good to know, I had an issue when I tried that, but thinking back it was a ssh version incompatibility between the default windows and ubuntu.
Or just use a hardware key and enable touch to sign so you have to touch it for every action even when it's unlocked
100% agreed.
For me, the stakes are very low. It's my windows "gaming" machine, and has access to a few low-value hosts.
Otherwise I'd invest the time to learn wtf is pageant ;D
If the hosts are under your control, and never connect to untrusted hosts, then you are ok. The user authentication is encrypted, so the signatures are not visible to a man in the middle.