-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pyhanko-certvalidator] Ability to skip nonce validation in OCSP response #321
Comments
Some additional notes:
|
EDIT: oops, clicked the submit button a bit too early
Yes, that's by design (as it is intended to the default). You can, however, initialise (and resource-manage) your own fetchers and pass those to the validation context. Does that work for you?
That's definitely a bug. Can you post a sample stack trace here? |
Thanks for the idea. This worked for me:
|
Issue
One of the CAs I'm working with currently has an incorrect implementation of the nonce extension for OCSP. They are responding with the nonce value, but it's always the same. I suspect this might be because the response is cached on the CA's side. This leads to OCSPValidationError being raised in
certvalidator
. There are also some issues related to this in the wbond/certvalidator repo.Proposed Solution
Add an option in the
ValidationContext
to disable nonce extension entirely. If this sounds okay, I can make a Pull Request for the same :)The text was updated successfully, but these errors were encountered: