-
Notifications
You must be signed in to change notification settings - Fork 10
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: receive Intel & AMD CRLs in attestation report #159
Conversation
71d7378
to
1ade461
Compare
1ade461
to
90e866e
Compare
dd0f51d
to
9afd39a
Compare
9afd39a
to
6cfcc3d
Compare
6cfcc3d
to
291e4ac
Compare
8a8dacf
to
a4eed6d
Compare
@puiterwijk please double-check the loop, as I noticed that some intermediate certs are failing the CRL signature check. The logic:
Example of when it succeeds:
Example when it fails:
The issuer is different in the failure case, but the cert had the same CRL URL. |
a4eed6d
to
6a5f725
Compare
6a5f725
to
d8164fc
Compare
Seems that I have an issue where the wrong CRL is used to validate intermediate certs. I've made a tool to help me debug what's going on: https://github.com/rjzak/cert-buddy. So far, the CRL format on-disk is fine. |
d8164fc
to
eee34f8
Compare
9e894d1
to
c1efdf1
Compare
Progress: CRLs are now passing for Intel. AMD isn't working as the root CRL is used for intermediate & end certificates, so a different CRL selection strategy is needed. |
d9cfe78
to
60a09ed
Compare
9dd9ffa
to
584d387
Compare
584d387
to
6732b2d
Compare
Signed-off-by: Richard Zak <[email protected]>
6732b2d
to
38af218
Compare
Depends on:
Refs:
Blocking:
Edit: CRL validation disabled for now to permit new deployments of Enarx, Steward, Drawbridge. Enabling of CRL validation will be a subsequent PR.
Signed-off-by: Richard Zak [email protected]