-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add ML-KEM 512, 768, and 1024 #539
base: main
Are you sure you want to change the base?
Conversation
021e1cd
to
b474f2a
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #539 +/- ##
==========================================
- Coverage 95.80% 92.62% -3.18%
==========================================
Files 61 67 +6
Lines 8143 9366 +1223
Branches 0 9366 +9366
==========================================
+ Hits 7801 8675 +874
- Misses 342 420 +78
- Partials 0 271 +271 ☔ View full report in Codecov by Sentry. |
#[cfg(feature = "fips")] | ||
mod missing_nid { | ||
pub const NID_MLKEM512: i32 = 988; | ||
pub const NID_MLKEM768: i32 = 989; | ||
pub const NID_MLKEM1024: i32 = 990; | ||
} |
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.
Is this to account for any AWS-LC versions that may have the NID_MLKEM*
define missing?
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.
Correct. aws-lc-fips-sys
is aligned with the AWS-LC-FIPS 2.0.x, which doesn't provide these constants.
Co-authored-by: Samuel Chiang <[email protected]>
Issues:
Resolves #ISSUE-NUMBER1
Addresses #ISSUE-NUMBER2
Description of changes:
Describe current behavior and how your code changes that behavior. If there are no issues this pr is resolving, explain why this change is necessary.
Call-outs:
Point out areas that need special attention or support during the review process. Discuss architecture or design changes.
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.