letsencrypt / letsencrypt/boulder
Build tool to simulate retrieving certificate status via grpc streaming for mass revocation event
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
We don't have a full grasp of the crl-updater performance characteristics during a mass revocation event. We should build a tool that uses grpc streaming to retrieve certificate status analogous to the crl-updater without producing a CRL. To get a worst case approximation, the tool should be able to take two timestamps and retrieve all certificate statuses issued by given intermediate cert or that used a specific challenge type between the timestamps.
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 tracing the crl-updater and its gRPC streaming behavior to understand how certificate statuses are retrieved without producing a CRL. Define the tool's timestamp, intermediate-certificate, and challenge-type inputs, then verify that it can retrieve all matching statuses during the selected interval and measure worst-case performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- backend, devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100