-
Notifications
You must be signed in to change notification settings - Fork 393
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
"Algorithm negotiation fail" on sftp #88
Comments
I can confirm this bug - funnily enough also with DomainFactory... |
I asked DomainFactory. They updated some server components. Since then, they use stronger SSL ciphers. Which fits with the error message "algorithm negotiatian fail". So please @PhilippC , could you check if support for the stronger ciphers is possible? Which are, according to the blog entry:
Thanks |
I guess, then the problem could be solved by simply updating the JSch-component, which is (iirc) right now at 0.1.50. According to their Change-Log, 0.1.51 and 0.1.52 seem to introduce those missing KexAlgorithms, we're looking for (except for curve). |
Hi! This is also an issue to me. Could you please update JSch to the latest version (0.1.54)? JSch 0.1.50 was released on May 9, 2013 (almost 5 years ago!) and does not support modern TLS/SSL cipher suites. We don't want to use outdated insecure cipher suites. I can help out with testing. Thanks! |
There is already #48 on the milestone list for 1.05 that should (hopefully) take care of this issue. |
just found #1812 as a duplicate of this issue. I'm closing this, howevre, because the other one has more upvotes. |
I get "Algorithm negotiation fail" on a sftp connection, which has not been changed for months. User+Password are correct, e.g. FileZilla on PC or the sftp-Plugin for TotalCommander on the phone works fine with the same credentials. A new "file open" doesn't work, with the same message. Any idea?
Provider is DomainFactory. Contact me if you want a test account or more information. German is fine.
Thanks
The text was updated successfully, but these errors were encountered: