letsencrypt / letsencrypt/boulder
Boulder-Observer: Add CR, and Certificate probers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
To replace some additional existing infrastructure with Boulder Observer, we'd want to add three more things to probe:
- The validity and remaining lifetime of the CRL at a given URL
- The remaining lifetime of the certificate presented at a given URL
- The revocation status of the certificate presented at a given URL
For specific results, we would probably want to write Prometheus alerts to ensure that the lifetime of expired-isrgrootx1.l.o was negative, and that the cert for revoked-isrgrootx2.l.o appears in a CRL, and of course the more normal cases.
----(tracking added by @beautifulentropy)----
- TLS validity (https://github.com/letsencrypt/boulder/pull/7120)
- CRL validity (https://github.com/letsencrypt/boulder/pull/6349)
- Certificate Revocation Status
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 reading Boulder Observer's existing TLS and CRL validity probers, which are marked complete in the checklist. Trace how their results are exposed for alerting, then add the remaining certificate revocation status probe. Done means the certificate for revoked-isrgrootx2.l.o is reported as present in a CRL while normal cases remain distinguishable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100