Enable OpenSSL to load a configuration file during initialization #168
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
filipecosta90
approved these changes
Feb 2, 2022
yossigo
approved these changes
Feb 3, 2022
|
Thanks @slice4e! |
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.
Enable OpenSSL to load a configuration file using the standard openssl.cnf file.
In this way, we can change the default OpenSSL ENGINE, as well as configure other capabilities.
This aligns memtier benchmark to a similarly added capability in Redis here : redis/redis#8143
By providing this capability to memtier benchmark, we can ensure that memtier benchmark and redis are using the same OpenSSL configuration (e.g. ENGINE) while performing a test.