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

Provide a hint as to the likely cause of failure to find a valid issuer #206

Open
briansmith opened this issue Mar 24, 2021 · 0 comments
Open

Comments

@briansmith
Copy link
Owner

Multiple times people have asked for a way to learn something more than UnknownIssuer when webpki fails to build a path. For example, if the end-entity certificate is signed using an algorithm that wasn't enabled, them it would be useful to get an "certificate signed with an unsupported algorithm" error instead of just getting "unknown issuer." So far I've avoided doing this because it adds complexity in an attempt to provide precision that isn't, in general, warranted. However, it's true that often the more precise error is more useful for diagnosing a configuration issue than "unknown issuer" is.

Previously, we considered logic similar to what Firefox does: If every attempt to build a path fails for the same reason, then return that reason; otherwise, return "unknown issuer" like today. We should reconsider doing at least this.

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

1 participant