make signing with libsecp256k1 the default #14
Merged
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
sign_compact also uses libsecp256k1 signing with openssl is still possible using sign_with_openssl() and sign_compact_with_openssl() added call to secp256k1_context_randomize(), this protects from potential future side channel attacks.
This was referenced Nov 28, 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.
libsecp256k1 becomes hard dependency - won't load without it.
sign_compact (used by SignMessage) and recover_compact (used by VerifyMessage) now also uses libsecp256k1
signing with openssl is still possible using sign_with_openssl()
and sign_compact_with_openssl()
added call to secp256k1_context_randomize(), this protects from potential
future side channel attacks.