Skip to content

Simplify revocation (WIP) #10

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.

Sign up for GitHub

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

Open
ryancdickson wants to merge 10 commits into
base: main
Choose a base branch
from
Open

Simplify revocation (WIP) #10

Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
d6ce879
Update BR.md
ryancdickson Sep 29, 2025
4d39f5e
Update BR.md
ryancdickson Sep 29, 2025
8d26f51
Update BR.md
ryancdickson Sep 29, 2025
2159543
Update BR.md
ryancdickson Sep 29, 2025
c216864
Update BR.md
ryancdickson Sep 29, 2025
4b3d7f6
Update BR.md
ryancdickson Sep 29, 2025
c43e03c
Update BR.md
ryancdickson Sep 29, 2025
704729f
Update BR.md
ryancdickson Sep 29, 2025
7716f79
Update BR.md
ryancdickson Sep 29, 2025
ffaaeb6
Update BR.md
ryancdickson Sep 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 23 additions & 35 deletions docs/BR.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1490,28 +1490,16 @@ No stipulation.

The CA MAY support revocation of Short-lived Subscriber Certificates.

With the exception of Short-lived Subscriber Certificates, the CA SHALL revoke a Certificate within 24 hours and use the corresponding CRLReason (see Section 7.2.2) if one or more of the following occurs:

1. The Subscriber requests in writing, without specifying a CRLreason, that the CA revoke the Certificate (CRLReason "unspecified (0)" which results in no reasonCode extension being provided in the CRL);
2. The Subscriber notifies the CA that the original certificate request was not authorized and does not retroactively grant authorization (CRLReason #9, privilegeWithdrawn);
3. The CA obtains evidence that the Subscriber's Private Key corresponding to the Public Key in the Certificate suffered a Key Compromise (CRLReason #1, keyCompromise);
4. The CA is made aware of a demonstrated or proven method that can easily compute the Subscriber's Private Key based on the Public Key in the Certificate, including but not limited to those identified in [Section 6.1.1.3(5)](#6113-subscriber-key-pair-generation) (CRLReason #1, keyCompromise);
5. The CA obtains evidence that the validation of domain authorization or control for any Fully-Qualified Domain Name or IP address in the Certificate should not be relied upon (CRLReason #4, superseded).

With the exception of Short-lived Subscriber Certificates, the CA SHOULD revoke a certificate within 24 hours and MUST revoke a Certificate within 5 days and use the corresponding CRLReason (see Section 7.2.2) if one or more of the following occurs:

6. The Certificate no longer complies with the requirements of [Section 6.1.5](#615-key-sizes) and [Section 6.1.6](#616-public-key-parameters-generation-and-quality-checking) (CRLReason #4, superseded);
7. The CA obtains evidence that the Certificate was misused (CRLReason #9, privilegeWithdrawn);
8. The CA is made aware that a Subscriber has violated one or more of its material obligations under the Subscriber Agreement or Terms of Use (CRLReason #9, privilegeWithdrawn);
9. The CA is made aware of any circumstance indicating that use of a Fully-Qualified Domain Name or IP address in the Certificate is no longer legally permitted (e.g. a court or arbitrator has revoked a Domain Name Registrant's right to use the Domain Name, a relevant licensing or services agreement between the Domain Name Registrant and the Applicant has terminated, or the Domain Name Registrant has failed to renew the Domain Name) (CRLReason #5, cessationOfOperation);
10. The CA is made aware that a Wildcard Certificate has been used to authenticate a fraudulently misleading subordinate Fully-Qualified Domain Name (CRLReason #9, privilegeWithdrawn);
11. The CA is made aware of a material change in the information contained in the Certificate (CRLReason #9, privilegeWithdrawn);
12. The CA is made aware that the Certificate was not issued in accordance with these Requirements or the CA's Certificate Policy or Certification Practice Statement (CRLReason #4, superseded);
13. The CA determines or is made aware that any of the information appearing in the Certificate is inaccurate (CRLReason #9, privilegeWithdrawn);
14. The CA's right to issue Certificates under these Requirements expires or is revoked or terminated, unless the CA has made arrangements to continue maintaining the CRL/OCSP Repository (CRLReason "unspecified (0)" which results in no reasonCode extension being provided in the CRL);
15. Revocation is required by the CA's Certificate Policy and/or Certification Practice Statement for a reason that is not otherwise required to be specified by this section 4.9.1.1 (CRLReason "unspecified (0)" which results in no reasonCode extension being provided in the CRL); or
16. The CA is made aware of a demonstrated or proven method that exposes the Subscriber's Private Key to compromise or if there is clear evidence that the specific method used to generate the Private Key was flawed (CRLReason #1, keyCompromise).

With the exception of Short-lived Subscriber Certificates, the CA MUST revoke a Certificate in accordance with the following:

| **#** | **Description of Revocation Event** | **Revocation Timeline** | **RFC 5280 `reasonCode`** |
| :---: | --- | --- | :---: |
| 1 | The CA obtains evidence of either: <br><br>(A) the Subscriber's Private Key corresponding to the Public Key in the Certificate suffered a Key Compromise <br><br>OR<br><br>(B) a demonstrated or proven method that can easily compute the Subscriber's Private Key based on the Public Key in the Certificate. | MUST within 24 hours | `keyCompromise` (1) |
| 2 | The CA obtains evidence that either of the following should not be relied upon: <br><br>(A) the validation of domain authorization or control for any fully‐qualified domain name or IP address in the Certificate <br><br>OR<br><br> (B) the CA's authority to issue a Certificate for the requested domain(s) or IP address(es) in the Certificate. | MUST within 24 hours | `privilegeWithdrawn` (9) |
| 3 | The CA is made aware that the Certificate was not issued in accordance with either: <br><br>(A) these Requirements<br><br>OR<br><br>(B) the CA's Certificate Policy or Certification Practice Statement. | SHOULD within 24 hours, but MUST within 5 days | `cessationOfOperation` (5) |
| 4 | The CA is made aware that the Subscriber's request, issuance, or use of a resulting Certificate has violated one or more of its material obligations under the Subscriber Agreement or Terms of Use. | SHOULD within 24 hours, but MUST within 5 days | `affiliationChanged` (3) |
| 5 | Either:<br><br>(A) The Subscriber requests revocation in writing, without specifying a CRLreason, and the circumstances for the request do not meet the immediately above criteria <br><br>OR<br><br>(B) for any other reason, and the circumstances for the request do not meet the immediately above criteria. | SHOULD within 24 hours, but MUST within 5 days | `unspecified` (0) |

#### 4.9.1.2 Reasons for Revoking a Subordinate CA Certificate

The Issuing CA SHALL revoke a Subordinate CA Certificate within seven (7) days if one or more of the following occurs:
Expand Down Expand Up @@ -3602,27 +3590,27 @@ Table: crlEntryExtensions Component

| __CRL Entry Extension__ | __Presence__ | __Description__ |
| --- | -- | ----- |
| `reasonCode` | * | When present (OID 2.5.29.21), MUST NOT be marked critical and MUST indicate the most appropriate reason for revocation of the Certificate. <br><br> MUST be present unless the CRL entry is for a Certificate not technically capable of causing issuance and either 1) the CRL entry is for a Subscriber Certificate subject to these Requirements revoked prior to July 15, 2023 or 2) the reason for revocation (i.e., reasonCode) is unspecified (0). <br><br>See the "CRLReasons" table for additional requirements. |
| `reasonCode` | * | When present (OID 2.5.29.21), MUST NOT be marked critical and MUST indicate the most appropriate reason for revocation of the Certificate. <br><br> MUST be present unless the reason for revocation (i.e., reasonCode) is unspecified (0). <br><br>See Section 4.9.1 for additional requirements. |
| Any other value | NOT RECOMMENDED | - |

Table: CRLReasons
For any certificate revoked on or after 20XX-XX-XX, the reasonCode extension, if present, MUST contain one of the values specified below. The extension MUST be included for all permitted reasons except for unspecified (0).

| __RFC 5280 reasonCode__ | __RFC 5280 reasonCode value__ | __Description__ |
| --- | - | ------ |
| unspecified | 0 | Represented by the omission of a reasonCode. MUST be omitted if the CRL entry is for a Certificate not technically capable of causing issuance unless the CRL entry is for a Subscriber Certificate subject to these Requirements revoked prior to July 15, 2023.
| keyCompromise | 1 | Indicates that it is known or suspected that the Subscriber’s Private Key has been compromised. |
| affiliationChanged | 3 | Indicates that the Subject's name or other Subject Identity Information in the Certificate has changed, but there is no cause to suspect that the Certificate's Private Key has been compromised. |
| superseded | 4 | Indicates that the Certificate is being replaced because: the Subscriber has requested a new Certificate, the CA has reasonable evidence that the validation of domain authorization or control for any fully‐qualified domain name or IP address in the Certificate should not be relied upon, or the CA has revoked the Certificate for compliance reasons such as the Certificate does not comply with these Baseline Requirements or the CA's CP or CPS. |
| cessationOfOperation | 5 | Indicates that the website with the Certificate is shut down prior to the expiration of the Certificate, or if the Subscriber no longer owns or controls the Domain Name in the Certificate prior to the expiration of the Certificate.
| certificateHold | 6 | MUST NOT be included if the CRL entry is for 1) a Certificate subject to these Requirements, or 2) a Certificate not subject to these Requirements and was either A) issued on-or-after 2020-09-30 or B) has a `notBefore` on-or-after 2020-09-30.
| privilegeWithdrawn | 9 | Indicates that there has been a subscriber-side infraction that has not resulted in keyCompromise, such as the Certificate Subscriber provided misleading information in their Certificate Request or has not upheld their material obligations under the Subscriber Agreement or Terms of Use. |
Table: Permitted reasonCode Values

The Subscriber Agreement, or an online resource referenced therein, MUST inform Subscribers about the revocation reason options listed above and provide explanation about when to choose each option. Tools that the CA provides to the Subscriber MUST allow for these options to be easily specified when the Subscriber requests revocation of their Certificate, with the default value being that no revocation reason is provided (i.e. the default corresponds to the CRLReason "unspecified (0)" which results in no reasonCode extension being provided in the CRL).
| __RFC 5280 reasonCode__ | __RFC 5280 reasonCode value__ |
| --- | - |
| unspecified | 0 |
| keyCompromise | 1 |
| affiliationChanged | 3 |
| cessationOfOperation | 5 |
| privilegeWithdrawn | 9 |

The privilegeWithdrawn reasonCode SHOULD NOT be made available to the Subscriber as a revocation reason option, because the use of this reasonCode is determined by the CA and not the Subscriber.
In cases where multiple reasonCodes are considered appropriate for a revocation, keyCompromise and privilegeWithdrawn reasons MUST take precedence, and in that order.

When a CA obtains verifiable evidence of Key Compromise for a Certificate whose CRL entry does not contain a reasonCode extension or has a reasonCode extension with a non-keyCompromise reason, the CA SHOULD update the CRL entry to enter keyCompromise as the CRLReason in the reasonCode extension.

The Subscriber Agreement, or an online resource referenced therein, MUST inform Subscribers about the revocation reason options listed above and provide explanation about when to choose each option. Tools that the CA provides to the Subscriber MUST allow for these options to be easily specified when the Subscriber requests revocation of their Certificate, with the default value being that no revocation reason is provided (i.e. the default corresponds to the CRLReason "unspecified (0)" which results in no reasonCode extension being provided in the CRL).

#### 7.2.2.1 CRL Issuing Distribution Point

Partitioned CRLs MUST contain an Issuing Distribution Point extension. The `distributionPoint` field of the Issuing Distribution Point extension MUST be present. Additionally, the `fullName` field of the DistributionPointName value MUST be present, and its value MUST conform to the following requirements:
Expand Down