gnutls, setting priority via --ciphers #16557
Closed
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
|
I think this feels like the most sensible approach. I approve. |
No longer ignore the `--ciphers` argument in gnutls curl builds, but use it to set the gnutls priority string. When the set ciphers start with '+', '-' or '!', it is *appended* to the curl generated priority string. Otherwise it replaces the curl one completely. Add test_17_18 to check various combinations.
bagder
approved these changes
Mar 5, 2025
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.
No longer ignore the
--ciphersargument in gnutls curl builds, but use it to set the gnutls priority string.When the set ciphers start with '+', '-' or '!', it is appended to the curl generated priority string. Otherwise it replaces the curl one completely.
Add test_17_18 to check various combinations.
Added documentation.