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
Comments
Ticket retargeted after milestone closed |
I can confirm this issue. As a workaround select any certificate in the bookmark settings. |
Ticket retargeted after milestone closed |
Milestone renamed |
Ticket retargeted after milestone closed |
Milestone renamed |
Ticket retargeted after milestone closed |
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
andrequire_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
The text was updated successfully, but these errors were encountered: