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

Unable to reach a settlement for key exchange #9947

Closed
cyberduck opened this issue May 18, 2017 · 5 comments
Closed

Unable to reach a settlement for key exchange #9947

cyberduck opened this issue May 18, 2017 · 5 comments
Assignees
Labels
bug sftp SFTP Protocol Implementation thirdparty Issue caused by third party
Milestone

Comments

@cyberduck
Copy link
Collaborator

7e9117a created the issue

This is happening with two SFTP accounts. Both worked fine for many months and as recently as last week.

No settings have been changed. Both accounts can be accessed normally, with no issues, using other FTP client apps. With CyberDuck I receive this error message:

Unable to reach a settlement: [diffie-hellman-group14-sha1, diffie-hellman-group1-sha1] and [diffie-hellaman-group-exchange-sha256]. The connection attempt was rejected. The server may be down, or your network may not be properly configured.

Note: I don't know who diffie-hellman-group is. These don't appear to be certificates for me or my hosts.

I did contact the hosting provider. It was established that normal connection is possible by using other FTP clients.

Thank you.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

It looks like the server responds with spelling error in the proposed key exchange algorithm. It should be diffie-hellman-group-exchange-sha256 but not diffie-hellaman-group-exchange-sha256. Therefore the negotiation of the key exchange algorithm fails.

@cyberduck
Copy link
Collaborator Author

7e9117a commented

Replying to [comment:3 dkocher]:

It looks like the server responds with spelling error in the proposed key exchange algorithm. It should be diffie-hellman-group-exchange-sha256 but not diffie-hellaman-group-exchange-sha256. Therefore the negotiation of the key exchange algorithm fails.

Thank you for investigating this. Do you know the cause or the solution yet?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 ScottStearns]:

Replying to [comment:3 dkocher]:

It looks like the server responds with spelling error in the proposed key exchange algorithm. It should be diffie-hellman-group-exchange-sha256 but not diffie-hellaman-group-exchange-sha256. Therefore the negotiation of the key exchange algorithm fails.

Thank you for investigating this. Do you know the cause or the solution yet?
The cause looks to be a bug in the server software.

@cyberduck
Copy link
Collaborator Author

7e9117a commented

Thank you, which server? The problem persists when I attempt to use Cyberduck. The issue doesn't exist accessing the hosting server from FileZilla or via other means.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The server of your SFTP account. Please contact the hosting service provider for a fix.

@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.
Labels
bug sftp SFTP Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants