Skip to content

Make digitalSignature KU optional for Subordinate CA Certificates #363

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

Merged
aarongable merged 1 commit into from
Oct 29, 2026
Merged

Make digitalSignature KU optional for Subordinate CA Certificates #363

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion CP-CPS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1072,7 +1072,7 @@ All ISRG Certificates are issued in accordance with one of the following Certifi
|         `certificatePolicies` | Contains only the Baseline Requirements Domain Validated Reserved Policy Identifier (OID 2.23.140.1.2.1) |
|         `crlDistributionPoints` | Contains the HTTP URI of a CRL issued by the Issuing CA whose scope includes this certificate |
|         `extKeyUsage` | Contains only `id-kp-serverAuth` (OID 1.3.6.1.5.5.7.3.1) |
|         `keyUsage` | Critical, with only the `digitalSignature` (0), `keyCertSign` (5), and `cRLSign` (6) bits set |
|         `keyUsage` | Critical, with only the `keyCertSign` (5), `cRLSign` (6), and optionally `digitalSignature` (0) bits set |
|         `subjectKeyIdentifier` | Contains a truncated hash of the `subjectPublicKey`, per Section 2(1) of RFC 7093 |
|         Any other extension | Not present |
| `signatureAlgorithm` | Byte-for-byte identical to the `tbsCertificate.signature` |
Expand Down
Loading