-
Notifications
You must be signed in to change notification settings - Fork 5.6k
tls: include every CA in the trusted bundle when generating TLS session IDs #47405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ggreenway
merged 1 commit into
envoyproxy:main
from
abhinav-phi:tls-session-id-all-ca-certs
Sep 15, 2026
+84
−7
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
8 changes: 8 additions & 0 deletions
8
changelogs/current/bug_fixes/tls__session-id-digest-covers-all-ca-certs.rst
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| Fixed TLS session ID generation so that every CA certificate in the trusted CA bundle, not | ||
| just the first one, contributes to the digest that keys resumable sessions. Previously a | ||
| change to any CA after the first -- for example rotating or removing a trust anchor through | ||
| an xDS update -- left previously issued session IDs valid, allowing a resumed session to be | ||
| accepted without validation against the updated trust bundle. Configurations with a single | ||
| CA produce byte-identical session IDs to the previous behavior; configurations with a | ||
| multi-certificate bundle will issue new session IDs once after the upgrade, causing a | ||
| one-time increase in full handshakes. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this field still necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is still needed, but only for first-CA reporting.
ca_cert_is assigned at default_validator.cc:224 and read bygetCaCertInformation(),initializeCertExpirationStats()anddaysUntilFirstCertExpires(). Now that the digest no longer uses it, it is only a duplicate reference toshared_ca_certs_->certs[0](CaCertCache::getOrCreate() never returns an empty bundle), so those three can read the first entry of the shared bundle directly and the member can be dropped.Happy to push that as an extra commit on this PR, but it is a pure no-behavior-change refactor of the cert-info/expiration reporting path, so say the word if you would rather keep this PR limited to the digest fix and see it as a separate change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not needed. BTW since this sounds like Claude, please disclose the AI usage.