Skip to content

Clarify the security of the ecdsa_verify functions for secp256k1 and P256#1391

Merged
sagar-a16z merged 3 commits intoa16z:mainfrom
mathmasterzach:clarify-curve-ops
Apr 1, 2026
Merged

Clarify the security of the ecdsa_verify functions for secp256k1 and P256#1391
sagar-a16z merged 3 commits intoa16z:mainfrom
mathmasterzach:clarify-curve-ops

Conversation

@mathmasterzach
Copy link
Copy Markdown
Contributor

Added comments to

  1. explicitly indicate that ecdsa_verify assumes inputs are well formed and
  2. point out where the well-formedness of the inputs is assured in the examples

mathmasterzach and others added 2 commits March 31, 2026 18:24
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
@sagar-a16z sagar-a16z merged commit 877ea54 into a16z:main Apr 1, 2026
20 checks passed
@mathmasterzach mathmasterzach deleted the clarify-curve-ops branch April 1, 2026 15:17
0xAndoroid added a commit that referenced this pull request Apr 2, 2026
Move input validation into ecdsa_verify() for both secp256k1 and P-256,
and restrict _unchecked constructors to pub(crate). Addresses the security
footgun documented in PR #1391.
@0xAndoroid 0xAndoroid mentioned this pull request Apr 2, 2026
2 tasks
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