milksad
/
rust-secp256k1-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity

Clarify the documentation of `normalize_s` 

I was reading the docs for `normalize_s` and got confused what the
point was - it says that libsecp "will only accept" signatures that
are normalized, which led me to believe it would refuse to
deserialize such signatures. This is untrue, it only refuses to
*validate* such signatures.
This commit is contained in:
Matt Corallo 2023-04-20 02:46:18 +00:00
parent 141b874e65
commit f6c68ec329
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/ecdsa/mod.rs
View File

@ -124,8 +124,8 @@ impl Signature {
/// changing even the signature itself can be a problem. Such applications /// changing even the signature itself can be a problem. Such applications
/// require a "strong signature". It is believed that ECDSA is a strong /// require a "strong signature". It is believed that ECDSA is a strong
/// signature except for this ambiguity in the sign of s, so to accommodate /// signature except for this ambiguity in the sign of s, so to accommodate
/// these applications libsecp256k1 will only accept signatures for which /// these applications libsecp256k1 considers signatures for which s is in
/// s is in the lower half of the field range. This eliminates the /// the upper half of the field range invalid. This eliminates the
/// ambiguity. /// ambiguity.
/// ///
/// However, for some systems, signatures with high s-values are considered /// However, for some systems, signatures with high s-values are considered