Implement RFC8410: Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure

[stevefan1999-personal]

https://datatracker.ietf.org/doc/html/rfc8410

We can workaround this by using a wrapper that implements https://docs.rs/spki/latest/spki/trait.DynSignatureAlgorithmIdentifier.html...

[juliusl]

I submitted a PR for ed25519-dalek;

However, one thing I noticed though is that after implementing DynSignatureAlgorithmIdentifier x509-cert still needs ed25519::Signature to implement SignatureBitStringEncoding in order to build certificates with SigningKey/VerifyingKey. I worked around this in my PR but I'm not sure if it's better to fix ed25519 first or to just fix the issue in this crate.

[juliusl]

Realized that the x509 should've probably been a separate issue so I removed it from the PR

[tarcieri]

I worked around this in my PR but I'm not sure if it's better to fix ed25519 first or to just fix the issue in this crate.

@juliusl if you can add support in the ed25519 crate that would be great. I will try to open a tracking issue for that.

Edit: opened an upstream issue: RustCrypto/signatures#888