letsencrypt / letsencrypt/boulder
cert-checker: Detect if a certificate was issued by a revoked intermediate after the revocation time
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
The 2023 key ceremony is going to generate an intermediate, immediately revoke it, and never have it configured in Boulder, but we still need a plan for the eventuality of an active intermediate needing to be revoked.
Contributor guide
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
Start by locating the cert-checker implementation and reading how certificate issuance and intermediate revocation are currently represented. Trace how revocation time is handled, then define and verify behavior for certificates issued by an intermediate after that time. The issue provides no named files or tests, so the relevant entry points and completion checks still need to be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100