OCSPValidationError is not handled
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
When certvalidator fetches an OCSP response, but request and response nonces do not match OCSPValidationError is raised:
However, this error is neither caught (and handled), nor documented.
Note: Other OCSP related errors are converted into derived exceptions (OCSPValidationIndeterminateError and OCSPNoMatchesError) which are handled in validate._validate_path:
However, its not clear for me how not matching nonces should be handled at the end.
Contributor guide
No contributing guide indexed for this repository
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 certvalidator/ocsp_client.py at lines 101-103 and validate.py around validate._validate_path at lines 375-397. Trace how OCSPValidationError differs from the other OCSP exceptions and determine the intended handling for a nonce mismatch. Done means the mismatch is handled consistently with the validation flow and its behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100