Addresses #7881: removing weaker ciphers #10353
Open
+2
−6
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
marvin-tigera
added
release-note-required
|
|
|
Wouldn't it be possible to also remove |
|
I believe @lucastigera is looking at making this configurable. I don't think we can make a default set that is going to satisfy everyone's needs. |
Wow, I see. That is very good news, and I think the best possible solution! |
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.
Description
This is a "bug" fix to address concerns from our security teams where weak and disallowed ciphers are showing up in Typha. Often we will configure ciphers at runtime , but that does not appear to be an option for this service.
Related issues/PRs
fixes #7881
Todos