ceremony: Add support for configuring cross-sign EKUs#8750
Open
aarongable wants to merge 2 commits intomainfrom
Open
ceremony: Add support for configuring cross-sign EKUs#8750aarongable wants to merge 2 commits intomainfrom
aarongable wants to merge 2 commits intomainfrom
Conversation
ezekiel
approved these changes
May 9, 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.
As of 2025-09-15, the CCADB policy requires that all subordinate CA certificates, including cross-signs of existing roots, must have an EKU extension. As of 2026-06-15, the Chrome policy will require that all new subordinate CA certificates only contain the tlsServerAuth EKU. This change allows us to configure the set of EKUs that will appear in a CA certificate, while restricting that selection per the aforementioned requirements.