Skip to content

Conversation

@Sushisource
Copy link
Member

What was changed

Don't enable native TLS roots if a CA override is specified. This is technically breaking, but only if you were doing a somewhat odd thing in the first place.

Why?

People using CA overrides often want to do it in an environment where there are no native roots, which this change enables.

Checklist

  1. Closes [Bug] Native certs used for TLS client even when server root CA override present #1004

  2. How was this tested:
    Could not come up with any kind of reasonable test that wasn't dramatically more LOC than it feels worth. Open to ideas.

  3. Any docs updates needed?

@Sushisource Sushisource requested a review from a team as a code owner September 10, 2025 00:45
Copy link
Member

@cretz cretz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SDKs need to call out this breaking change in their release notes when they update Core. Not sure how we can make sure they do.

@Sushisource
Copy link
Member Author

SDKs need to call out this breaking change in their release notes when they update Core. Not sure how we can make sure they do.

That's what the 💥 is for, and I hope when people update they see it in the log, but, yeah, we might want a script for that or something.

@Sushisource Sushisource merged commit 30a2741 into master Sep 10, 2025
18 checks passed
@Sushisource Sushisource deleted the tls-no-native-on-override branch September 10, 2025 16:30
@adeal
Copy link

adeal commented Sep 10, 2025

Thank you @cretz @Sushisource!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Native certs used for TLS client even when server root CA override present

5 participants