letsencrypt / letsencrypt/boulder
CA should mark itself unhealthy after a certain number of signing failures
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Note that this wouldn't give us a way to become healthy again, but it would cause all the clients of the CA to send traffic to other CAs. We would need to make sure we have a daytime alert for this case, since it would require manual intervention eventually. This mitigates a problem where single boulder-ca instance has a problem reaching the HSM but other instances can still reach the HSM.
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
The issue names no files, tests, failure threshold, or alert entry point. Start by locating the CA signing and health-status paths, then clarify the failure threshold and alerting behavior. Done means repeated signing failures mark the instance unhealthy and the operational alert and manual-recovery path are defined and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100