-
Notifications
You must be signed in to change notification settings - Fork 148
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 exchange encryption keys #254
Comments
I have encountered the same question, but on Windows 11. Is there anyone who knows how to deal with the issuse? Thx. |
I'm encountering the same issue on Windows 11:
This code works when connecting to some machines but not others. I can connect to Ubuntu 20.04 but connecting to Ubuntu 22.04 fails with the error above. I'm using "vendored-openssl" and this same code works fine on recent MacOS to connect to both distros. If there are any other logs or diagnostics that would be helpful to diagnose this, let me know. |
What were you two trying to connect to? What type of keys were you trying to use if any? |
Same error here, I'm not passing any encryption key
I'm using window 10 and trying to connect to Ubuntu 22.04.1 LTS |
I have the same issue on windows 11 trying to connect to Arch Linux with kernel 6.0.10 |
same here |
Seen the same issue on CentOS. Isn't this related to libssh2/libssh2#1020 ? |
Having the same issue using Windows 10. |
I was having this issue connecting to a Juniper switch (EX4100-F-12T) from Windows 11. I was able to resolve it by adding this config bit to my Juniper device:
|
There's a good chance this is related in many cases to #323; some distros/systems are only enabling encrypt-then-MAC MACs now. A workaround may be to add e.g. hmac-sha2-256 / hmac-sha2-512 to the "MACs" table in sshd_config. These are considered somewhat less secure than the -etm counterparts, but encrypt-then-mac isn't supported until this library is updated to use ssh2 1.11.0. |
Problematic on ubuntu 22.04, { code: Session(-5), msg: "Unable to exchange encryption keys" }
The text was updated successfully, but these errors were encountered: