Store the size of the allocated private key buffer for ML-KEM#10206
Merged
dgarske merged 1 commit intowolfSSL:masterfrom Apr 14, 2026
Merged
Store the size of the allocated private key buffer for ML-KEM#10206dgarske merged 1 commit intowolfSSL:masterfrom
dgarske merged 1 commit intowolfSSL:masterfrom
Conversation
dgarske
previously approved these changes
Apr 13, 2026
SparkiDev
previously requested changes
Apr 13, 2026
Frauschi
force-pushed
the
mlkem-dynamic-key-2
branch
from
abf0a71 to
17ba0c2
Compare
dgarske
approved these changes
Apr 14, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Follow-up for #10179: when
WOLFSSL_MLKEM_DYNAMIC_KEYSis enabled, store the size of the allocated private key buffer for laterForceZero()calls. This prevents potential erroneous corruption via a wrongkparameter.