letsencrypt / letsencrypt/boulder
Consider logging the SPKI hash at issuance time for easier log searches
@ezekiel is already working on this.
Since Sep 8, 2026.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
The SPKI hash is what we use to identify compromised keys: it's one of the more common input methods to the admin block-key tool, and it's what we store in the blockedKeys table. But it's good to get a sense of what certs will be affected before blocking a key, querying the keyHashToSerial table can be slow, and running queries directly against the database is generally a bad practice.
So what if we could do that same query via logs in our log query system instead? If we include the SPKI hash in our issuance logs it'll be very easy for our log search to quickly identify all affected certificates in the last 90 days.
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.
Assessment
This issue has not been assessed yet.