this post was submitted on 26 Oct 2024
327 points (94.8% liked)
Programmer Humor
19557 readers
592 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
id_rsa shouldn't exist any more.
If I had a nickel for every time I had to change my ssh key algorithm I'd have two nickels.
Which isn't much but it's concerning that it happened twice.
A few days ago I was messing with my ubiquiti dream router and its ssh config option said the key should start with ssh-rsa 🙄
It probably accepts other key types and it's just the UI that's outdated. I doubt they're using an SSH implementation other than Dropbear or OpenSSH, and both support ed25519.
Could be stupid input validation which requires
^ssh-rsaFact of the matter is RSA is perfectly secure still...and ECDSA/ED25519 should also be extinct given the rising need for post quantum cryptography
The problem is not the RSA math itself but that it is both extremely slow and implementing it is particularly susceptible to bugs and side channel attacks https://blog.trailofbits.com/2019/07/08/fuck-rsa/
Most of the situations I encounter RSA are in projects where I hope RSA is implemented correctly. I have a lot of Let's Encrypt certs that are still RSA and my main SSH keys are still RSA. All of these were generated quite some time ago. I understand the problem with projects that implement it incorrectly but I'd hope OpenSSH and certbot aren't those projects 😥
For Certbot, I think it's even further up the chain - OpenSSL. And if you're installing it to Apache or Nginx, its probably just OpenSSL again.
Azure DevOps only allows you to use RSA keys. This caused a major outage in May (they switched from V1 to V2) :).