key: don't use Hasher
to generate fingerprints; just use hashes
crate
#726
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.
In addition to changing
SecretKey
andSharedSecret
to usehashes
, we also unconditionally use the public half ofKeyPair
as a fingerprint, since that's always available and does not need extra deps.This patches the existing unit tests but doesn't add more. Maybe they should be removed; it's a bit weird to have unit tests for
Debug
output. But in this case we're doing some nontrivial logic and I guess we wanted to double-check that it was taking effect.I'd also like to change the manual tagged-hash implementation to use
bitcoin_hashes
methods but those are under construction rust-bitcoin/rust-bitcoin#3184 and the existing stuff is neither faster nor less code than what's currently done. So we'll live with it.Fixes #725