Upgrade Your SSH Key to Ed25519 (2018)
21–30 of 41 posts
Re: Upgrade Your SSH Key to Ed25519 (2018)
#22Interesting note: Packaged versions of GPG2 did not support ED25519 keys at the time this was written. Additionally some major openpgp packages (notably Golangs) does (or did not) support ED25519 at the time of writing either.[0] This caused the death of a bit of software I was working on because one engineer insisted on using his ED25519 key which my software could not cope with and I was not smart enough to fix it…
Re: Upgrade Your SSH Key to Ed25519 (2018)
#23> If it was more than five years ago and you generated your SSH key with the default options, you probably ended up using RSA algorithm with key-size less than 2048 bits long. It's closer to 16 years, for OpenSSH [1]. > Open up your terminal and type the following command to generate a new SSH key that uses Ed25519 algorithm: > Generate SSH key with Ed25519 key type That's broken in an amusing way. But speaking of br…
Pray tell?
Re: Upgrade Your SSH Key to Ed25519 (2018)
#24Re: Upgrade Your SSH Key to Ed25519 (2018)
#25> If it was more than five years ago and you generated your SSH key with the default options, you probably ended up using RSA algorithm with key-size less than 2048 bits long. It's closer to 16 years, for OpenSSH [1]. > Open up your terminal and type the following command to generate a new SSH key that uses Ed25519 algorithm: > Generate SSH key with Ed25519 key type That's broken in an amusing way. But speaking of br…
Re: Upgrade Your SSH Key to Ed25519 (2018)
#26Sure in that national level entities could in theory crack 1024 RSA. They would be stupid to tie up such a valuable resource for a year or so on breaking a single SSH connection. They would instead use it on something that got them thousands or even millions of connections.
>If it has 3072 or 4096-bit length, then you’re good. Less than that, you probably want to upgrade it.
There is zero evidence that anyone will ever break 2048 bit RSA short of some sort of huge breakthrough. I don't know where these claims are coming from...
Re: Upgrade Your SSH Key to Ed25519 (2018)
#27> If it was more than five years ago and you generated your SSH key with the default options, you probably ended up using RSA algorithm with key-size less than 2048 bits long. It's closer to 16 years, for OpenSSH [1]. > Open up your terminal and type the following command to generate a new SSH key that uses Ed25519 algorithm: > Generate SSH key with Ed25519 key type That's broken in an amusing way. But speaking of br…
gnome-keyring on Ubuntu 21.04 supports my ed25519 SSH key just fine.
Re: Upgrade Your SSH Key to Ed25519 (2018)
#28> If it was more than five years ago and you generated your SSH key with the default options, you probably ended up using RSA algorithm with key-size less than 2048 bits long. It's closer to 16 years, for OpenSSH [1]. > Open up your terminal and type the following command to generate a new SSH key that uses Ed25519 algorithm: > Generate SSH key with Ed25519 key type That's broken in an amusing way. But speaking of br…
> That's broken in an amusing way. Pray tell?
Re: Upgrade Your SSH Key to Ed25519 (2018)
#29Re: Upgrade Your SSH Key to Ed25519 (2018)
#30>The 1024-bit length is even considered unsafe. Sure in that national level entities could in theory crack 1024 RSA. They would be stupid to tie up such a valuable resource for a year or so on breaking a single SSH connection. They would instead use it on something that got them thousands or even millions of connections. >If it has 3072 or 4096-bit length, then you’re good. Less than that, you probably want to upgrad…
It's about being cautious. If we want secure systems for the masses, we need to advance cryptographic defenses faster than we have proofs the attackers are advancing.
Most crypto we consider broken today "had zero evidence that anyone would ever break it" before it actually happened...