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

Jump to bottom

Hostname verification (SSL) trust is not working properly #3001

Closed
cyberduck opened this issue Feb 18, 2009 · 2 comments
Closed

Hostname verification (SSL) trust is not working properly #3001

cyberduck opened this issue Feb 18, 2009 · 2 comments
Assignees
@dkocher
Labels
bug duplicate ftp-tls FTP (TLS) Protocol Implementation high priority

Comments

@cyberduck
Copy link
Collaborator

76b0620 created the issue

Hi,

after updating to 3.1.2 the self signed SSL certificate of my server works only in a very limited way. Each file or connection pops up the certificate acception prompt and the always trust option does not work.

Cheers

CaOsKid
@cyberduck
Copy link
Collaborator Author

@dkocher commented

This might be because the certificate has expired. Then the Always trust feature does not work as expected. Otherwise you have to restart Cyberduck to make it see the newly updated trust setting from the Keychain.

Also refer to #2938.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As a workaround to accept any certificate without verification you can issue the following command in Terminal.app window and restart Cyberduck.

defaults write ch.sudo.cyberduck ftp.tls.acceptAnyCertificate true

@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.
Assignees

@dkocher dkocher

Labels
bug duplicate ftp-tls FTP (TLS) Protocol Implementation high priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck