Ensure we don't block TLS 1.3 negotiation - #2792
Merged
Merged
Conversation
🤖 GitHub commentsJust comment with:
|
smith
approved these changes
Aug 21, 2026
This was referenced Sep 1, 2026
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
2 participants
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.
Don't block TLS 1.3 negotiation on any target framework
Previously, the agent explicitly restricted outgoing HTTPS connections to TLS 1.2, which prevented TLS 1.3 from being negotiated even on operating systems that support it (e.g., Windows 11+). This affected all supported target frameworks.
This change lets the operating system pick the best available TLS protocol (matching Microsoft's recommended best practice), instead of hardcoding TLS 1.2. As a result, the agent can now use TLS 1.3 where the OS/runtime supports it, while still working the same as before everywhere else.
Note for consumers: environments that require TLS 1.2 as a strict minimum via OS/registry policy should ensure that's configured at the OS level, since the agent no longer forces it independently of the OS configuration.