Make digitalSignature optional for TLS Subordinate CA Certificate Profile

Open Beginner friendly
#347 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet

Research direction

Start by reading the TLS Subordinate CA Certificate Profile in the CP-CPS and compare its digitalSignature requirement with CA/B Forum Baseline Requirements section 7.2.1.7. Done means the CP-CPS permits digitalSignature to be omitted for future TLS Subordinate CA Certificates and reflects the stated OCSP context.

Written by the indexing model from the issue text.

Description

In the BRs, it is permitted but not required, with a footnote saying "If a CA Certificate does not assert the digitalSignature bit, the CA Private Key MUST NOT be used to sign an OCSP Response." Now that we don't do OCSP, we don't need digitalSignature in future TLS Subordinate CA Certificates, and we can make it optional in the CP-CPS.

https://cabforum.org/working-groups/server/baseline-requirements/requirements/#712107-ca-certificate-key-usage

https://letsencrypt.org/documents/isrg-cp-cps-v6.1/#tls-subordinate-ca-certificate-profile

Dominant language
Python
Stars
38
Forks
26
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from letsencrypt/cp-cps

All issues in letsencrypt/cp-cps

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.