Repository navigation
ZOOKEEPER-5054: Netty client should allow every supported TLS ciphers - #2404
Merged
Merged
Conversation
Contributor
|
Re-running failed CI jobs. |
Contributor
|
Test needs JDK11+ to work properly, hence this PR is blocked by #2376 |
Contributor
|
We've abandoned this issue for quite a while. @meszibalu would you like to rebase it? |
We allow every supported ciphers at the client-side by default. This change does not affect the server-side and still allows to override the allowed ciphers at client-side.
meszibalu
force-pushed
the
zookeeper-5054
branch
from
September 30, 2026 11:19
04790c1 to
f5ffa56
Compare
Contributor
Author
|
@anmolnar Done. |
Contributor
|
Merged to |
Contributor
Author
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
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.
We allow every supported ciphers at the client-side by default. This change does not affect the server-side and still allows to override the allowed ciphers at client-side.