letsencrypt / letsencrypt/boulder
add tool to issue and revoke twice with different revocation reasons
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
One of the subtle things in the new Mozilla revocation reasons is that certificates can change their revocation reason if the new revocation reason is keyCompromise. We have integration tests for this but we should have a standalone tool that can check against a live ACME server: issue, check OCSP, revoke for non-keyCompromise, check OCSP, revoke for keyCompromise, check OCSP.
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 reading the existing integration tests for Mozilla revocation reasons and the code paths for issuing certificates, checking OCSP, and revoking certificates against a live ACME server. Done means a standalone tool performs the full sequence: issue, check OCSP, revoke with a non-keyCompromise reason, check OCSP, revoke with keyCompromise, and check OCSP again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100