Document signing secret-key validity precondition#1229
Merged
Conversation
This was referenced Jun 26, 2026
Contributor
CBMC Results (ML-DSA-44, REDUCE-RAM)Full Results (206 proofs)
|
Contributor
CBMC Results (ML-DSA-65, REDUCE-RAM)Full Results (206 proofs)
|
Contributor
CBMC Results (ML-DSA-87, REDUCE-RAM)Full Results (206 proofs)
|
Contributor
CBMC Results (ML-DSA-65)Full Results (206 proofs)
|
Contributor
CBMC Results (ML-DSA-44)Full Results (206 proofs)
|
Contributor
CBMC Results (ML-DSA-87)Full Results (206 proofs)
|
hanno-becker
requested changes
Jun 27, 2026
hanno-becker
left a comment
Contributor
There was a problem hiding this comment.
Thank you @fegge, I support this change. One could even make the comment more prominent, see comment. @mkannwischer wdyt
Signing APIs assume a valid, bit-packed secret key and do not perform full serialized-key validation (t0, tr, s1, s2). Callers importing serialized keys can validate them via pk_from_sk before signing. * Add @warning notices to all sign* / signature* / pre_hash sign entry points in mldsa_native.h and mldsa/src/sign.h, and reword the sk parameter descriptions to "assumed to be valid". * Expand the Wycheproof client comment for the InvalidPrivateKey skip: FIPS 204 does not require signing to validate serialized private keys, full validation covers t0 and tr and is exposed through pk_from_sk, and those vectors are still tested via pkFromSk. Signed-off-by: Fredrik Dahlgren <fredrik.dahlgren@trailofbits.com> [hbecker: rebase+squash, adjust commit message] Signed-off-by: Hanno Becker <beckphan@amazon.co.uk>
b3f019d to
abf2742
Compare
mkannwischer
approved these changes
Jul 13, 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
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.
Summary
pk_from_skwhen they need to validate a serialized secret key before signing.InvalidPrivateKeysigning vectors are skipped whilepkFromSkstill tests those keys.Validation
clang-format -i mldsa/src/sign.h mldsa/mldsa_native.h: passedruff format test/wycheproof/wycheproof_client.py: passedruff check test/wycheproof/wycheproof_client.py: passedpython3 -m py_compile test/wycheproof/wycheproof_client.py: passedgit diff --check -- mldsa/src/sign.h mldsa/mldsa_native.h test/wycheproof/wycheproof_client.py: passedmake run_func -j4: passedmake wycheproof -j4: passedpython3 test/wycheproof/wycheproof_client.py --data-dir <fresh-temp-dir>: passed./scripts/formatbecausenixpkgs-fmtis not installed in this local environment./scripts/lintbecauseshfmtis not installed in this local environmentFixes #1216
This work was completed by Trail of Bits as part of the Patch The Planet project in collaboration with OpenAI. The issue was identified primarily by the Codex coding agent, and manually reviewed before submission.