Upgrade Your SSH Keys

blog.g3rt.nl

63 points·hackmin··8 comments

On Windows use PuTTY at own risk in 2021. It was an important tool two decades ago, but its time has sunset.

Windows 10 has "real" OpenSSH client available as a built-in feature (and server available as an optional feature). Use Windows Terminal (or ConEmu/Cmder, per preference) for the terminal experience upgrades PuTTY used to provide.

I use PuTTY because I'm used to it, and I use a ed25519 key with it without any issues.

Is there a way to make Ctrl+Space work with Windows Terminal? I recall it is converted to another key sequence by Windows before getting sent to the other side.

A quick search shows the Windows Terminal specific parts of the bug have been fixed: https://github.com/microsoft/terminal/issues/2865

Also a lot of suggestions in that quick search to try Ctrl+2 or Ctrl+@ as an alternative.

I keep seeing "EdDSA is faster than RSA" but is it ever usefully faster? I imagine it's maybe milliseconds of difference per secure connection initialization, and so it feels deceptive to market it as (usefully) faster.

Created a bash script to check existing keys, create new more secure key, protect existing keys with password.

https://github.com/pforret/bumpkeys

(2016)

And OpenWRT dropbear only just recently got ed25519 support at mainline. Not in a release yet.

I bumped into this recently when I replaced my older rsa hardware keys with newer models. Switched to openssh for now.

Reply on news.ycombinator.com