-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: ocsp revocation against merkle root & intermediate hashes #228
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
discussed.
ping me again when the changes are done and I'll approve this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍
🎉 This PR is included in version 7.10.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
- Implement handling of `OCSP_RESPONDER` type of revocation for OA v3 documents - Add tests for DID-issued OA v3 documents with OCSP_RESPONDER type of revocation - Housekeeping of filenames for fixtures BREAKING CHANGE: the old OCSP Responder implementation (where it checks by by document id instead of merkle root & intermediate hashes) is now deprecated It is no longer possible to perform OCSP revocation by document id as mentioned in #228 Fixes #243
Context
What does this PR do?
isRevokedByOcspResponder2()
to check against merkle root and intermediate hashes of a documentisRevokedByOcspResponder()
if OCSP Responder response is not recognised (To be removed in the future)