• Björn Tantau
      link
      fedilink
      385 months ago

      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.

    • @[email protected]
      link
      fedilink
      English
      23
      edit-2
      5 months ago

      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 🙄

      • @[email protected]
        link
        fedilink
        195 months ago

        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.

        • dbx12
          link
          fedilink
          25 months ago

          Could be stupid input validation which requires ^ssh-rsa

    • @[email protected]
      link
      fedilink
      125 months ago

      Fact of the matter is RSA is perfectly secure still…and ECDSA/ED25519 should also be extinct given the rising need for post quantum cryptography

        • @[email protected]
          link
          fedilink
          15 months ago

          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 😥

          • @[email protected]
            link
            fedilink
            English
            15 months ago

            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.

    • 🍆 💦
      link
      fedilink
      25 months ago

      Azure DevOps only allows you to use RSA keys. This caused a major outage in May (they switched from V1 to V2) :).