-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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 connect to old cisco switches: Unknown DH Group #9830
Comments
Check out #9810 |
Tried the nightly, still having the same issue. |
have you enabled the diffie-hellman-group1-sha1 kex in the profile settings in the nightly version? |
Yes, I did. |
Could you please post the output of connection setup log when connecting to the switch with |
here it is: PS C:\Users*> ssh -v -oKexAlgorithms=+diffie-hellman-group1-sha1 -c3des-cbc *********** Banner debug1: Authentications that can continue: password |
Thanks - a new nightly with 3DES cipher support should be ready soon: https://github.com/Eugeny/tabby/actions/runs/10395680351
|
Tried this new build, now it only says "disconnect". |
I've updated the build to show more detailed error messages - would appreciate if you could give it another try ✌️ |
@tiagocasalribeiro just curious, is the command "ip ssh version 2" present on the switch you are trying to connect to ? I bumped into a similar issue with the experimental build and some old devices without ssh server version 2 by default. It seems that the old ssh2 lib wasnt bother by the version ssh. |
Now I am getting this: Selecting ssh-rsa on the cyphers pane, I can now connect. Before it worked without it, weird... |
Thank you! I've added it to the defaults list |
Problem:
After upgrading to version 1.0.209 I am unable to connect to old switches, with Unknown DH Group. Read somewhere else it is an error related to BoringSSH used by EletronJS, that have dropped support for diffie-hellman-group1-sha1.
To Reproduce:
1 - Upgrade to version 1.0.209 or newer;
2 - Try to connect to an old Cisco switch.
The text was updated successfully, but these errors were encountered: