Skip to content

docs: improve signature malleability wording#153

Merged
cpu merged 1 commit intoC2SP:mainfrom
josibake:upstream-libsecp256k1-changes
Jul 31, 2025
Merged

docs: improve signature malleability wording#153
cpu merged 1 commit intoC2SP:mainfrom
josibake:upstream-libsecp256k1-changes

Conversation

@josibake
Copy link
Contributor

Apologies for the churn on this, but while reviewing the downstream PR to integrate #150, I noticed this comment seems incorrect.

I believe it should read something like the following to indicate these test vectors are only for implementations that do not tolerate signature malleability (corroborated by another reviewer here)

Update comment to indicate these test vectors should only be used for
implementations that _do not_ allow signature malleability. If an
implementation tolerates or even requires malleability, it should be
tested with a different set of test vectors.
Copy link
Member

@cpu cpu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This updated verbiage reads correctly to me as well. Thank you for following up on this upstream :-)

@cpu cpu merged commit 7ae4532 into C2SP:main Jul 31, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants