Allow OpenSSL::SSL::SSLContext#max_version to be set on SSL connections
#984
Conversation
This file contains hidden or 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
We've observed a kafka cluster that attempts to negotiate communication using TLS 1.3 but then fails. This requires us to pin the max version used to TLS 1.2.
|
Pull request has been marked as stale due to a lack of activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We've observed a kafka cluster that attempts to negotiate communication using TLS 1.3 but then fails. This requires us to pin the max version used to TLS 1.2. Currently we're doing that via a monkey patch module prepended onto
Kafka::SslContextbut we'd prefer to have an argument to configure this directly.