letsencrypt / letsencrypt/boulder
Tear out TemporallyShardedSerialPrefixes
Open
Nobody has claimed this yet.
starter
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
We have a bunch of scaffolding to support the transition from temporally-sharded to explicitly-sharded CRLs. That transition was done on March 12 2025, so the last temporally-sharded certificate expired in June. We can now remove this extra layer of complexity.
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 searching the Go repository for TemporallyShardedSerialPrefixes and tracing every reference to the temporally-sharded CRL scaffolding. Use the explicitly-sharded CRL transition as context; done means the obsolete layer and its references are removed without disrupting the current CRL path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100