-
Notifications
You must be signed in to change notification settings - Fork 454
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
Add support for revocation checking via OCSP #446
Comments
I updated my code to support SSLyze 3.0.8, working example at https://gist.github.com/gattjoe/509971b9df8cd088cbb68f6fbbab9949 |
Finally had time to look at this - it looks good and as stated in your email, it would make more sense as a standalone plugin. |
@nabla-c0d3 Desn't nassl already support this (implemented in ...
"ocsp_response": {
"certificate_status": "good",
"extensions": null,
"hash_algorithm": "sha1",
"issuer_key_hash": "5168FF90AF0207753CCCD9656462A212B859723B",
"issuer_name_hash": "CF26F518FAC97E8F8CB342E01C2F6A109E8E5F0A",
"next_update": "2020-10-11T14:18:01",
"produced_at": "2020-10-04T15:03:01",
"responder_id": "5168FF90AF0207753CCCD9656462A212B859723B",
"serial_number": "06D754AE96D28371A4DEF60AC211B3E1",
"status": "SUCCESSFUL",
"this_update": "2020-10-04T15:03:01",
"type": "Basic OCSP Response",
"version": 1
},
... Is this different from what's expected? I'm confused. |
@faheel I think the existing functionality built into SSLyze is to check for OCSP responses from the server (if the server is configured to provide one). This is via OCSP stapling. Run the same query above against github.com:
github is not setup with OCSP stapling. The functionality requested here will ask the OCSP responder from the issuing cert authority for an OCSP status. I wrote a quick python package to do just that until the functionality is built directly into SSLyze, check out https://github.com/MetLife/OCSPChecker. |
@gattjoe Got it. Thanks for the clarification! |
Sample code on how to do it at https://gist.github.com/gattjoe/94dbf531d3d4ef60ca8a2f3663382926
The text was updated successfully, but these errors were encountered: