SC105: Remove High Risk language from TLS BR and EVG - #678
Open
srdavidson wants to merge 7 commits into
Open
Conversation
This was referenced Aug 19, 2026
romanf
reviewed
Aug 21, 2026
|
|
||
| ##### 3.2.2.12.1 High Risk Status | ||
|
|
||
| The High Risk Certificate requirements of Section 4.2.1 of the Baseline Requirements apply equally to EV Certificates. |
There was a problem hiding this comment.
I propose to remove this chapter and re-number the following chapters.
There seems to be no reference to this or the following chapters in any other CA/B document, so re-numbering would not have side-effects.
I if removal is not desirable, then I would put "No stipulation." as it's done in the TLS BR (e.g. 1.4.2).
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.
No description provided.