Update to k256 0.14 pre-release to allow high-S in recover pubkey #2015
Conversation
This file contains 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
webmaster128
force-pushed
the
fix-pubkey-recovery-high-s-0.14
branch
from
3b6f279
to
dc06e0c
Compare
webmaster128
force-pushed
the
add-wycheproof
branch
from
5ecf3d3
to
0e9624a
Compare
webmaster128
changed the title
webmaster128
force-pushed
the
fix-pubkey-recovery-high-s-0.14
branch
from
dc06e0c
to
c5a943b
Compare
|
Closing in favour of a fresh ticket for later: #2018 |
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.
Alternative to #2014 , using a 0.14 pre-release of k256. As discussed in RustCrypto/elliptic-curves#991, no changes to the
VerifyingKey::recover_from_digestcall are needed.Requires Rust 1.73.0 or higher
This does not update contracts since that would lead to huge merge conflicts in Lockfiles.