-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
SSL handshake failure caused by unknown certificate authority of provided client certificate does not indicate selected certificate #14169
Comments
Requested a logfile and got this message over and over, as described in #14198 Not sure if this logged error is related, as the error does not include the URL it is complaining about, and so it's a guess. |
Got a logfile from the end user, looks like this.
Mountain duck is choosing a client certificate, submitting it to the server, which rejects with "unknown CA". What mountain duck isn't doing is telling us which client cert was actually used, and what chain was in place, if any. When dealing with non technical people, this lack of detail makes troubleshooting very difficult. |
Describe the bug
If any security failure exists when connecting to a server over TLS, details of certificates involved need to be made available in a sensible fashion that is practical to troubleshoot.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Details of the certificate involved need to be made available in such a way that they can be screenshotted and/or downloaded and sent by a user to someone who can troubleshoot this.
In this case, the correct certificate is properly trusted, and works fine for everyone else and other services. It is very possible there is a man in the middle going on here, but it's almost impossible to troubleshoot because the certificate mountain duck is complaining about is kept hidden.
Screenshots

Desktop (please complete the following information):
Log Files
Additional context
The text was updated successfully, but these errors were encountered: