-
Notifications
You must be signed in to change notification settings - Fork 742
feat: add integration test for secp384r1_mlkem_1024 #5438
New issue
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
Conversation
|
||
#[cfg(feature = "pq")] | ||
mod mldsa; | ||
mod pq; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably fine for a temporary hack, but it seems sad that we have an entire "features" folder but we're going to shove all the features into one module. If we had a third feature that wasn't pq, what would we rename this module to? "misc"? The more correct way to handle this would probably be to move any code you need to reuse out of mldsa so you can have a separate mlkem file specifically for mlkem tests.
Resolved issues:
resolves #5432
Description of changes:
Adds integration tests for validating ML-KEM hybrid key exchange interoperability between s2n-tls and OpenSSL 3.5.
Previously, there were no automated tests verifying negotiation of the
SecP384r1MLKEM1024
KEM group between s2n-tls and OpenSSL clients/servers. This PR adds two integration tests:These tests confirm a successful handshakes and verifies the negotiated KEM group
SecP384r1MLKEM1024
.Call-outs:
Adding integration tests for PR #5395
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.