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
Describe the bug Pure ML-DSA algorithm IDs (TLS and OIDs) don't match values from current IETF drafts
To Reproduce Create a x.509 cert with ML-DSA key. Connect with ML-DSA signature algorithms in TLS.
Neither use the algorithm identifiers from current IETF drafts
Expected behavior ML-DSA keys (PKCS#8) and certificates (X.509) should use OIDs from draft-ietf-lamps-dilithium-certificates-05.
TLS connections should use Signature Scheme IDs from draft-tls-westerbaan-mldsa-00
Environment (please complete the following information): Looking at current master: https://github.com/open-quantum-safe/oqs-provider/blob/98ec7fc3e1f194b9df4760eccc1ca2cf2c0dc16b/oqs-template/oqs-sig-info.md
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Pure ML-DSA algorithm IDs (TLS and OIDs) don't match values from current IETF drafts
To Reproduce
Create a x.509 cert with ML-DSA key.
Connect with ML-DSA signature algorithms in TLS.
Neither use the algorithm identifiers from current IETF drafts
Expected behavior
ML-DSA keys (PKCS#8) and certificates (X.509) should use OIDs from draft-ietf-lamps-dilithium-certificates-05.
TLS connections should use Signature Scheme IDs from draft-tls-westerbaan-mldsa-00
Environment (please complete the following information):
Looking at current master:
https://github.com/open-quantum-safe/oqs-provider/blob/98ec7fc3e1f194b9df4760eccc1ca2cf2c0dc16b/oqs-template/oqs-sig-info.md
The text was updated successfully, but these errors were encountered: