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
As specified in https://datatracker.ietf.org/doc/html/draft-ietf-lamps-x509-shbs-00:
pk-XMSS-HashSig PUBLIC-KEY ::= { IDENTIFIER id-alg-xmss-hashsig KEY XMSS-HashSig-PublicKey PARAMS ARE absent CERT-KEY-USAGE { digitalSignature, nonRepudiation, keyCertSign, cRLSign } } XMSS-HashSig-PublicKey ::= OCTET STRING
And here the definition of SubjectPublicKeyInfo in RFC 5280
SubjectPublicKeyInfo ::= SEQUENCE { algorithm AlgorithmIdentifier, subjectPublicKey BIT STRING }
Shall the XMSS public key be an OCTET-STRING(public key bytes), or just the "public key bytes"?
This applies also to the XMSS-MT, HSS-LMS.
The text was updated successfully, but these errors were encountered:
draft-ietf-lamps-x509-shbs-00 is an early draft still, leave this open until it has matured.
Sorry, something went wrong.
No branches or pull requests
As specified in https://datatracker.ietf.org/doc/html/draft-ietf-lamps-x509-shbs-00:
And here the definition of SubjectPublicKeyInfo in RFC 5280
Shall the XMSS public key be an OCTET-STRING(public key bytes), or just the "public key bytes"?
This applies also to the XMSS-MT, HSS-LMS.
The text was updated successfully, but these errors were encountered: