Defer to system defaults for cipher suites with urllib3 2.0+ #2922
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.
Starting in urllib3 2.0, the hardcoded
DEFAULT_CIPHERS
for the ssl_context have been removed. This is a migration in a safer direction to allow user systems to define preferred cipher suites and enable modification without new releases of urllib3. This will expedite any security patching and give users finer grained control over what is chosen.Please note that botocore does not support urllib3 2.0 yet, but users are starting to see this interaction when testing for a future upgrade. To help enable that, we'll start deferring to urllib3 for this selection when an appropriate urllib3 version is installed (ref).