The comments about Ed25519 versus Ed448 were meant for the general case of their use, and not (necessarily) strictly in the use for SSH.
However, the reason for Ed25519 use in OpenSSH is because the keys are much smaller, and easier to cut/paste/etc, for the same security factor. The fact that they are faster for signing is a bonus.
All of the above correspond to roughly the security of AES 128. If you want AES 256 equivalence, double the size/length.
I'm in the habit of using ssh-copy-id(1), but there are a lot of places where you have to copy-paste in a web interface (and lots of instructions tell you to copy-paste into your remote ~/.ssh/authorized_keys file).
"Please note that, due to the structure of the underlying ASN.1 structure, RSA PEM bodies start always with the same characters: MIG for 1024 bit keys, MII for 2048 and 4096 bit ones."
Hmm, I wouldn’t think so, but I’m not an expert in such things. If you already have access to that text, you’ve won. I wouldn’t think that would leak any extra information.
However, the reason for Ed25519 use in OpenSSH is because the keys are much smaller, and easier to cut/paste/etc, for the same security factor. The fact that they are faster for signing is a bonus.
* https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-Se...
RFC 8032 § 7.1. Test Vectors for Ed25519:
RFC 8032 § 7.4. Test Vectors for Ed448 A comparable RSA 3072 key is much longer: * https://www.scottbrady91.com/openssl/creating-rsa-keys-using...* https://goteleport.com/blog/comparing-ssh-keys/
All of the above correspond to roughly the security of AES 128. If you want AES 256 equivalence, double the size/length.
I'm in the habit of using ssh-copy-id(1), but there are a lot of places where you have to copy-paste in a web interface (and lots of instructions tell you to copy-paste into your remote ~/.ssh/authorized_keys file).