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
Matching cipher is not supported: aes256-ctr #3271
Comments
Looks related to this issue: (http://forums.sun.com/thread.jspa?threadID=5393136). What is the selected cipher if you connect using
|
Supported ciphers by Cyberduck are (top has first priority, selection is depending on the match from the advertised ciphers from the server.
|
it looks like our cipher is aes128-cbc excerpt:
I wonder why it would seemingly stop after Cyberduck tries aes256-ctr? Do you need more info from the ssh -v transcript? Thank you.. |
I have a similar problem connecting to a SunOS 5.10 server using sftp (Cyberduck Version 3.2.1 (4923)). Grüsse aus dem Frankenland in Schweiz
|
Replying to [comment:5 wschulze@…]:
No wen don't read the preferred priorities from the OpenSSH configuration. |
Replying to [comment:5 wschulze@…]:
I would need a public reachable server to replicate this issue. I suppose I need no account to debug the key negotation failure. |
Same exact problem where I cannot connect to a server using SFTP since some change in Cyberduck some months ago. In my case, the cipher is different. Just now finding this support page as the lack of SFTP support prevents my use.
|
Replying to [comment:8 Cipher_aes128]:
Please post the output of |
Please reopen if you can supply the information above. |
After a recent patch was applied to our Solaris 10 software on our server, we can no longer connect to the server with Cyberduck using SFTP. Upon login, it immediately gives a, "I/O Error: Connection failed. There was a problem connecting to our server:22". Nothing is even listed in the Transcript.
In /var/adm/messages we are getting:
We are able to connect to the same server successfully using Fetch and Fugu. We are running SSH2.
Do we somehow need to reconfigure Cyberduck to handle a different cipher or to use SSH2 or ...?
We are running Mac OS 10.4.11 and 10.5, and Cyberduck Version 3.2 (4648) or later.
Thanks.
The text was updated successfully, but these errors were encountered: