Skip to content
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

Linting OCSP responses #458

Open
jsha opened this issue Jul 24, 2020 · 5 comments
Open

Linting OCSP responses #458

jsha opened this issue Jul 24, 2020 · 5 comments
Labels

Comments

@jsha
Copy link
Contributor

jsha commented Jul 24, 2020

In this bug, Apple shared a very thorough list of lints they apply to OCSP responses from their own issuance infrastructure. It would be useful to implement these in an open-source linter. Are the folks here interested in incorporating an OCSP linter into zlint? Do you think it would be better as a separate project?

@zakird
Copy link
Member

zakird commented Jul 24, 2020

This came up once in the past #382. I think the consensus is: Yes! We'd love to have them, but we should structure their addition such that they don't make running or maintaining existing certificate lints more difficult.

@cardonator
Copy link
Contributor

I think this fits into our sets of lints nicely, we could even exclude OCSP/CRL lints by default.

@Legrandin
Copy link

+1 for being able to linting CRLs too

@pgporada
Copy link
Contributor

We've been reviewing the entire corpus of Mozilla Bugzilla CA incidents and this has come up for another CA.

@kowshikRoy
Copy link
Contributor

kowshikRoy commented Nov 5, 2024

Hi Maintainers,
I would be happy to work on implementing OCSP linting. The question is:

  • Given that CAB Forum has made OCSP optional in v2.0.1 (SC63)

Please let me know. We're planning to implement something internally which we can think of contribute to zlint.
Let me know if there is interest?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants