-
Notifications
You must be signed in to change notification settings - Fork 729
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
Bump to secp256k1 0.20 and don't enable recovery
of secp256k1
in the dependency declaration
#545
Conversation
This version removes the fuzztarget and endomorphism features.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but I'd like to hear @stevenroose's opinion.
I think we meant to turn off the default features in our secp dep. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 8f071d1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
concept nack removing the feature - can you instead change this to disable the secp default features so that secp/recovery
actually does something?
I'm a bit curious @apoelstra, what's the thought behind feature-gating key recovery? There aren't any more deps afaik. Is it so unstable? I'm pretty sure that LN invoices use this and it seems to be fine. |
@sgeisler it pulls in the key recovery module from libsecp. This is morally an extra dep, and on code with a questionable patent story and no non-legacy usecases. If we had been better about feature-gating this historically maybe LN would not have used it :( |
4dab9d1
to
b5f1fda
Compare
secp-recovery
featurerecovery
of secp256k1
by default
Enabling this feature in the dependency declaration defeats the point of exposing a feature in rust-bitcoin that enables this because cargo currently does not provide a way to disable a once activated feature.
b5f1fda
to
e52e48e
Compare
recovery
of secp256k1
by defaultrecovery
of secp256k1
in the dependency declaration
Is e52e48e what you had in mind? |
Side note: removing a feature from defaults is also semver breaking (although this PR is breaking anyway). |
Yep, this looks great! Can you also add a commit which sets |
Actually we don't need this. See rust-bitcoin/rust-secp256k1#269 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack 8f071d1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really wish github would flag this somehow. It's bad enough that to get the "review changes" button you have to click to a page which hides all the commit IDs.
ack e52e48e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK e52e48e
rust-secp256k1
version 0.20 was recently released: rust-bitcoin/rust-secp256k1#257This PR updates
rust-bitcoin
to this latest version.