We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This draft appears to have the relevant information to implement PKCS#8 support: https://www.ietf.org/archive/id/draft-ietf-lamps-kyber-certificates-03.html
It should work in conjunction with the OIDs from here: https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registration
kems OBJECT IDENTIFIER ::= { nistAlgorithms 4 } [...] id-alg-ml-kem-512 OBJECT IDENTIFIER ::= { kems 1 } id-alg-ml-kem-768 OBJECT IDENTIFIER ::= { kems 2} id-alg-ml-kem-1024 OBJECT IDENTIFIER ::= { kems 3}
Note: the nistAlgorithms OID is 2.16.840.1.101.3.4.
nistAlgorithms
The pkcs8 crate should be sufficient for decoding/encoding PKCS#8 documents, although it would be nice to have some test vectors.
pkcs8
The text was updated successfully, but these errors were encountered:
tarcieri
bifurcation
No branches or pull requests
This draft appears to have the relevant information to implement PKCS#8 support: https://www.ietf.org/archive/id/draft-ietf-lamps-kyber-certificates-03.html
It should work in conjunction with the OIDs from here: https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registration
Note: the
nistAlgorithms
OID is 2.16.840.1.101.3.4.The
pkcs8
crate should be sufficient for decoding/encoding PKCS#8 documents, although it would be nice to have some test vectors.The text was updated successfully, but these errors were encountered: