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

Certificate chain displayed not complete #8885

Closed
cyberduck opened this issue Jun 18, 2015 · 5 comments
Closed

Certificate chain displayed not complete #8885

cyberduck opened this issue Jun 18, 2015 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 18, 2015

34092a6 created the issue

on OSX 10.10.3 and CyberDuck 4.8 (build 17762), clicking on the padlock button brings up a dialog box where the Certificate Heiarchy is not complete - it gets cut off at the Intermediate CA level - the actual target Server certificate details are not displayed at all.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 18, 2015

34092a6 commented

test server to reproduce the error:

https://dav.pixi.me/

(Platform) FreeBSD, Apache 2.4, mod_dav, OpenSSL 1.0.2c

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 18, 2015

@dkocher commented

We had this previously reported in #8698.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 18, 2015

@dkocher commented

This is possibly caused by change 58d0227. See also #8741.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 26, 2015

@dkocher commented

Added tests in 5fa980d.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 24, 2015

@dkocher commented

In 3b98898.

@cyberduck cyberduck closed this Aug 24, 2015
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants