configure: Detect (and reject) LibreSSL #6244
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
|
utACK |
|
I know @gmaxwell puts a good amount of time into auditing new OpenSSL releases, so I think it's worth getting his opinion here. I suspect that at this point he and @sipa may be more comfortable relying on libsecp256k1 for consensus-critical functionality than forks of OpenSSL. I certainly may be wrong in that assumption, though. |
|
ACK. I think we should get this in until OpenSSL ceases to be used for the consensus. |
|
utACK. |
|
ok, ut ACK then. |
laanwj
added a commit
that referenced
this pull request
Jun 10, 2015
a5a81f7 configure: Detect (and reject) LibreSSL (Luke Dashjr)
reddink
pushed a commit
to reddcoin-project/reddcoin-3.10
that referenced
this pull request
May 27, 2020
Rebased-From: a5a81f7 Github-Pull: bitcoin#6244 (cherry picked from commit 09334e0)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This hopefully won't make sense for 0.12, but do we want it for 0.11?