Basic fuzzing for C extraction of ML-KEM768 #554
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
BTW I won't be at all offended if you reject this as unsuitable for the project; like I said, this was mostly for my own paranoia. |
|
Nice, thanks!
Not at all. We'll need to find time to look at it. But this is great to have here! |
franziskuskiefer
approved these changes
Sep 19, 2024
|
Thanks! I did have a small error pointed out to me in one of the fuzz harnesses. I'll send a followup PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here are some very basic fuzzers for the main operations of the ML-KEM C extraction: public key validation, encapsulate and decapsulate. They aren't at all sophisticated, but I wrote them to double-check the soundness of the C extraction wrt undefined behaviour and memory safety. No findings after running over the weekend on 128 cores :)