Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix pubkey recovery to work with high/low s for k256 ^0.13.2 #2014

Merged
merged 2 commits into from
Feb 5, 2024

Conversation

webmaster128
Copy link
Member

@webmaster128 webmaster128 commented Feb 1, 2024

This is based on #2000 to get extra test coverage before marking the change. Merge #2000 first.

Closes #2010

@webmaster128 webmaster128 marked this pull request as ready for review February 5, 2024 13:24
Copy link
Collaborator

@chipshort chipshort left a comment

Choose a reason for hiding this comment

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

Code LGTM, was confirmed by the k256 maintainer and passes the new tests. Great!

@webmaster128 webmaster128 merged commit cc059dc into main Feb 5, 2024
27 checks passed
@webmaster128 webmaster128 deleted the fix-pubkey-recovery-high-s branch February 5, 2024 14:18
@CyberHoward
Copy link

Could this change be backported to the LTS (1.5) release?

We're running into issues using cosmwasm with other tooling due to the k256 version fix

@webmaster128
Copy link
Member Author

@mergify backport release/1.5

Copy link
Contributor

mergify bot commented Aug 5, 2024

backport release/1.5

✅ Backports have been created

@webmaster128
Copy link
Member Author

Yeah, makes sense. Backport here: #2198. Will be shipped in the next patch release.

webmaster128 added a commit that referenced this pull request Aug 6, 2024
Fix pubkey recovery to work with high/low s for k256 ^0.13.2 (backport #2014)
@webmaster128
Copy link
Member Author

Released in 1.5.6

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.

k256 v0.13.3 causes an error on secp256k1_recover_pubkey_works test
3 participants