-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix ML-DSA MakePublicKey derivation, verify guards, and ASN derivation testing #10985
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
Open
stenslae
wants to merge
1
commit into
wolfSSL:master
Choose a base branch
from
stenslae:fix-mldsa-privkey-derive-pubkey
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+707
−7
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🟡 [Medium] wc_EccPrivateKeyDecode now unconditionally derives the public point
💡 SUGGEST
apiThe decode of a SEC1 private-only key now performs a scalar point-multiplication on every call, changing
key->typefromECC_PRIVATEKEY_ONLYtoECC_PRIVATEKEYand adding a per-decode cost. This is the stated intent of the PR and errors are swallowed (best-effort, so no functional regression), but it is a behavioral/performance change to a widely-called public API (the identical change is duplicated in asn_orig.c:7707-7731). Any caller that asserted the key remained private-only after decode, or perf-sensitive bulk-decode paths, are affected. UnderECC_TIMING_RESISTANTit useskey->rng, whichwc_ecc_import_private_key_exdoes not set — so on timing-resistant builds the derivation silently runs unblinded / may no-op, which is acceptable as best-effort but worth documenting.Suggestion: Document the behavior change in the ChangeLog/API docs; consider whether the
key->rngreference on timing-resistant builds is meaningful given import does not populate it.