-
Notifications
You must be signed in to change notification settings - Fork 132
ML-KEM memory safety #2263
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
base: main
Are you sure you want to change the base?
ML-KEM memory safety #2263
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2263 +/- ##
==========================================
+ Coverage 78.81% 78.86% +0.05%
==========================================
Files 621 622 +1
Lines 108431 108664 +233
Branches 15398 15407 +9
==========================================
+ Hits 85462 85700 +238
+ Misses 22299 22294 -5
Partials 670 670 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
… memory-safety-ml-kem
… memory-safety-ml-kem
… memory-safety-ml-kem
Updated to resolve merge conflicts from #2176 (change in how parameters are being used, new functions that were added have length checks too). |
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.
clang-tidy made some suggestions
There were too many comments to post at once. Showing the first 10 out of 246. Check the log or trigger a new build to see more.
Description of changes:
Adds length parameters to ML KEM module to ensure allocated memory for various outputs is sufficient for generated results. Checks that already exist in higher levels for some functions were not removed.
Issues:
Resolves #CryptoAlg-2945
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.