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

FTPS explicit TLS no longer works without client certificate #10468

Open
cyberduck opened this issue Sep 20, 2018 · 10 comments
Open

FTPS explicit TLS no longer works without client certificate #10468

cyberduck opened this issue Sep 20, 2018 · 10 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 20, 2018

569de3b created the issue

A few years ago I set up an FTP server for a client, and tested with multiple FTP client software it works as expected with explicit TLS and passive transfers. Cyberduck has alway been my favourite file transfer client and it worked just fine.

Server side is setup with vsftpd and with default settings for ssl_request_cert=YES and require_cert=NO. The latter means (according to man page):
If set to yes, all SSL client connections are required to present a client certificate.

Cyberduck now asks me to point to a local certificate in my login keychain and wants to export it. Without completing this I'm no longer able to connect to the FTP server with Cyberduck. When I test this for my client with alternative tools like FileZilla and WinSCP I can still connect fine without configuring a client TLS cert.

This appears to be a bug, i think the use of a client cert should not be mandatory on the client unless the server requires it.

Best,
Martinus

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 15, 2019

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 22, 2019

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 30, 2019

@dkocher commented

#10671 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 2, 2019

@dkocher commented

I can confirm this issue. As a workaround select any certificate in the bookmark settings.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 11, 2019

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 25, 2019

@dkocher commented

#10875 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 2, 2020

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 2, 2020

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 2, 2020

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 26, 2021

@dkocher commented

Ticket retargeted after milestone closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants