letsencrypt / letsencrypt/cp-cps
Add caveat to section 6.1.2
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 38
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
We should add a caveat to section 6.1.2 to account for cases where ISRG is the subscriber (e.g. certs for valid/revoked/expired sites or certs for testing), in which case ISRG would generate and have access to the subscriber private key.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Find section 6.1.2 in the CP/CPS document and read its surrounding language about subscriber private-key access. Update the section to cover cases where ISRG is the subscriber, including valid, revoked, expired, or testing certificates, then verify the revised caveat is consistent with the surrounding text.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100