-
-
Notifications
You must be signed in to change notification settings - Fork 299
Support for PreferredAuthentications in OpenSSH configuration #9964
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
Comments
Ticket retargeted after milestone closed |
Please double check your bookmark settings does not have a private key selected for public key authentication that is tried first and may lead to an authentication failure if the server has limited the number of auth attempts. |
This issue has plagued me for a long time, to the extent that I use sshfs most of the time instead. If I check my server logs, I can see that Cyberduck tries all my ssh keys:
Despite that I did set
Command line sftp and sshfs works fine. Let me know if I can provide more information to help debugging this. I did try enable debug logging, but it didn't seem like it provided much additional information.
I'm using Cyberduck 7.6.1, but this has been an issue for a long, long time. |
Refer to OpenSSH Configuration Interoperability. We do not currently support the |
Milestone renamed |
Ticket retargeted after milestone closed |
Milestone renamed |
Milestone renamed |
This is a regression with builds 6.0.4 as well as 5.4.4. I had to revert to 5.2.2 which works as expected.
The problem:
I only have a password to authenticate against this SSH server. Command-line ssh used to give this error because it tries other client certificates before the server gives up. I had since then changed ~/.ssh/config to have these two lines
command-line ssh works fine. CyberDuck used to work fine but upgrading to latest build broke this.
The text was updated successfully, but these errors were encountered: