5 ms·

Hell, my company uses Azure repos, and they're still stuck on ssh-rsa keys: https://developercommunity.visualstudio.com/content/idea/365980/support-non-rsa-key

• b0afc375b5 5y ago
  Also aws: https://forums.aws.amazon.com/thread.jspa?threadID=250753 https://forums.aws.amazon.com/thread.jspa?threadID=250753
  • gspr 5y ago
    This isn't about wanting to replace RSA with Ed25519. The "ssh-rsa" method refers to RSA with SHA1 for hashing. It's the latter part that's the problem. The former is slightly inconvenient at worst (big keys).
    • b0afc375b5 5y ago
      Sure. But I was merely responding to the developercommunity forum post, which literally has the post body: > Currently only RSA keys are supported. The documentation doesn’t mention this fact; further, no error message is given when an *Ed25519* key is added. I wanted to express that this problem is not isolated to Azure.
• hannob 5y ago
  There's really nothing wrong with RSA keys. This issue is about the combination of RSA with SHA1 hashes for signatures. Using RSA with sha2-hashes is fine. (Yes, I know some people generally want to see RSA go away, but almost all more general issues with RSA have to do with encryption and not signatures, so SSH is pretty much unaffected.)
  • lxgr 5y ago
    > This issue is about the combination of RSA with SHA1 hashes for signatures. Is second preimage resistance actually relevant in the context of SSH authentication?
    • gruez 5y ago
      It's used by the client to authenticate the server, since openssh shows you the key fingerprint (hash) upon connecting, not the raw key.
      • lxgr 5y ago
        My client displays SHA256 fingerprints even for RSA servers. `.known_hosts` seems to store the full key anyway, not just a fingerprint.