Sunset for SHA-1 OCSP Signing
Open
Nobody has claimed this yet.
triaged: feature
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
https://cabforum.org/2022/01/26/ballot-sc53-sunset-for-sha-1-ocsp-signing/ is approved
We need to consider our security level checks in OCSP validation.
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 approved CA/B Forum Ballot SC53 and tracing the existing security-level checks used during OCSP validation. Done means the validation behavior accounts for the SHA-1 OCSP-signing sunset, but the issue does not name files or tests to use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100