letsencrypt / letsencrypt/boulder
Consider adding authorization revocation to admin-revoker
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
For incident response, it can be useful to revoke (set status = 4) either pending or already-finalized Authorizations. We should look into what it would take for admin-revoker to be able to handle this case, and now efficient it could be.
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 with the admin-revoker entry point and trace how Authorizations are currently handled. Investigate whether pending and already-finalized Authorizations can safely be set to status = 4, and assess the efficiency implications. Done means the supported behavior and its scope are clearly defined.
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