Resolve OpenSSL configuration issues #15
Merged
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.
The main goal here is to resolve a mysterious error some users would see when attempting to use embedded-redis that looks something like this:
The problem is that we were statically linking against libressl, which evidently struggles to parse certain stanzas in some OpenSSL configuration files. There's no mechanism to override the configuration file in play, and so users are stuck trying to comment out the parts of
/etc/ssl/openssl.cnf
that libressl finds offensive. It's a pretty gnarly situation.Our solution here is just to link directly against OpenSSL. It's possible that this is just trading one set of problems for another, but it certainly seems to resolve the most common known issue at the moment.
Since we need to generate new binaries anyhow, I took the opportunity to bump us up to Redis 6.2.7 while I was at it.