You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I Recently upgraded my main computer to Ubuntu 22.04, Jammy Jellyfish.
Then I was unable to login to my home node via ssh, and I got the error:
user@host:~ $ ssh kg6wxc-vc-rf-5g.local.mesh
Unable to negotiate with X.X.X.X port 2222: no matching host key type found. Their offer: ssh-rsa
According to google: The "host-key" signature type "ssh-rsa" refers to RSA with SHA-1, and SHA-1 is considered very weak.
I guess some systems are no longer going to accept the older algorithms.
There is a work around (for now, until it's support is dropped altogether).
I just had to add some lines to my local .ssh/config file:
I can then login to the AREDN device via ssh again.
I know, I know, we should not be using encryption, but ssh is kind of like a swiss army knife of networking, we kind of have to keep it, just for administrators sake!
dropbear may need to be updated or have it's configuration changed or something.
The text was updated successfully, but these errors were encountered:
Ha. ok.
That I did not try.
I'll upgrade and try again. 😄
Thx Tim. Sorry, I should have known you already addressed this.
I guess it's here now in case others hit the issue. 👍
I Recently upgraded my main computer to Ubuntu 22.04, Jammy Jellyfish.
Then I was unable to login to my home node via ssh, and I got the error:
According to google:
The "host-key" signature type "ssh-rsa" refers to RSA with SHA-1, and SHA-1 is considered very weak.
I guess some systems are no longer going to accept the older algorithms.
There is a work around (for now, until it's support is dropped altogether).
I just had to add some lines to my local
.ssh/config
file:I can then login to the AREDN device via ssh again.
I know, I know, we should not be using encryption, but ssh is kind of like a swiss army knife of networking, we kind of have to keep it, just for administrators sake!
dropbear
may need to be updated or have it's configuration changed or something.The text was updated successfully, but these errors were encountered: