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

Incorrect error message for unknown CAs #1

Open
BenBE opened this issue Aug 25, 2015 · 3 comments
Open

Incorrect error message for unknown CAs #1

BenBE opened this issue Aug 25, 2015 · 3 comments

Comments

@BenBE
Copy link

BenBE commented Aug 25, 2015

When testing the domain https://ssltest.security.fail/ the site wrongly issues a report that the chain is misconfigured. This indication is wrong: This can be verified by using DANE on the domain.

Three things to do:

  • Include the CA of that site
  • Support DANE
  • Maybe indicate that the chain may not be trusted/validated by everyone.

BUT: The chain itself is correct.

@AGWA
Copy link
Member

AGWA commented Aug 28, 2015

The error message is accurate: approximately zero clients support DANE or trust cacert.org, so virtually nobody can access that site, making it, for all intents and purposes, misconfigured.

@AGWA AGWA closed this as completed Aug 28, 2015
@BenBE
Copy link
Author

BenBE commented Aug 28, 2015

It's one question if the chain is configured correctly (including all necessary certificates) or if a client trusts it. As the chain is configured properly on the server (and includes all necessary certificates) the configuration is correct and thus the error message is misleading/wrong.

@AGWA
Copy link
Member

AGWA commented Aug 28, 2015

I see your point. Unfortunately, it's not trivial to distinguish these two cases. If the server sends a chain that's not signed by a trusted root, whatsmychaincert doesn't immediately know whether some other chain exists that is signed by a trusted root.

What it could do is try to construct an alternative chain using AIA to see whether an alternative trusted chain exists or not. But if the cert lacks AIA (which is the case with most private PKIs) then there's no way to know.

I'll re-open this ticket and work on it at some point.

@AGWA AGWA reopened this Aug 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants