-
Notifications
You must be signed in to change notification settings - Fork 741
Support secp256r1mlkem768
#2471
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
Benchmark resultsInstruction countsSignificant differencesClick to expand
Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Additional informationCheckout details:
|
Nice! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2471 +/- ##
==========================================
+ Coverage 95.27% 95.30% +0.03%
==========================================
Files 97 97
Lines 21359 21359
==========================================
+ Hits 20349 20356 +7
+ Misses 1010 1003 -7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
"Exercise" is used pointedly here to avoid suggestion that this is a meaningful test.
(added commit to exercise/cover this) |
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.
LGTM. A manual kick of the daily-tests run seems happy too.
This adds
rustls::crypto::aws_lc_rs::kx_group::SECP256R1MLKEM768
. It is added toALL_KX_GROUPS
, but notDEFAULT_KX_GROUPS
; this means that -- for now -- it requires explicit action to use (like plain MLKEM768).Generally I don't expect this to be widely deployed, and (eg) isn't supported right now by pq.cloudflareresearch.com. But I found that openquantumsafe.org does support it, so add a quick interop test with that server.
This also acts as a regression test for #2470