letsencrypt / letsencrypt/boulder
CT: Add support for fallback between an operator's logs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Today we only attempt to submit to one log from each operator. This limits our pool of potential logs, which can be a problem if some of those logs are experiencing uptime difficulties. It would be nice to be able to gracefully fail between logs run by the same operator, as long as we never end up actually including multiple SCTs from the same operator.
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 existing submission path that currently selects one log per operator. The change is complete when submission can fall back among that operator's logs during uptime failures without including multiple SCTs from the same operator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100