-
Couldn't load subscription status.
- Fork 100
feat: Certificate status assertion #1236
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
Conversation
…d picture with two ocsp responses
…number, need to figure out how to incorporate into SVI
…ificate serial number
… multiple ocsp_ders
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.
Looks good
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.
One request to keep this private to the crate for now, since I don't know how someone would use this publicly.
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.
We need a test that validates that the expected certificate status assertion gets added on signing and that it validates correctly when reading.
Reading validation could be done in a separate PR, but we need to ensure that the assertion is created under the right conditions here.
Changes in this pull request
Implements the Certificate Status assertion definition and support for checking for certificate revocation from ocsp values found in Certificate Status assertions.
Checklist
TO DOitems (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.