letsencrypt / letsencrypt/boulder
crl lints: add check that signature algorithm matches signer's public key type
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
https://bugzilla.mozilla.org/show_bug.cgi?id=1793441 has been filed because a CA has published a CRL issued from an ECDSA intermediate but with sha256WithRSAEncryption set as the signature algorithm. We should ensure we have a lint which checks for this circumstance.
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 the linked Bugzilla report and the repository's existing CRL lints. Add a lint for cases where the CRL signature algorithm does not match the signer's public key type, and verify that the mismatch is detected without rejecting valid CRLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100