4 ms·
> I don't think there's widespread support for X25519 (or X448) in X.509 certificates. The 2018 RFC if anyone is wondering: * https://tools.ietf.org/html/rfc8
by throw0101a 6y ago
> I don't think there's widespread support for X25519 (or X448) in X.509 certificates.
The 2018 RFC if anyone is wondering:
* https://tools.ietf.org/html/rfc8410 https://tools.ietf.org/html/rfc8410
- tialaramex 6y agoNote that this document is (of course) not an implementation, or even an explanation of how to implement support for this, but only a description of how to spell X25519 in ASN.1 in order to write it into a PKIX X.509 certificate. So this document is a precursor to widespread support for X25519 in certificates only in the same way that coming up with a name for your kid is a precursor to giving birth. It's not strictly necessary, and it's certainly not the most important thing you needed to do, but I guess it can be part of the process.
- GoblinSlayer 6y agoHuh? It doesn't write all the code for you, but it is an explanation, even provides an example of full certificate.
- tialaramex 6y agoYes, it explains how to write this down so that everybody agrees, we call this "spelling" by analogy to teaching a written language like English. It does not explain how to actually use any of this. RFC 8032 covers how to actually implement EdDSA, but that's a different document.