Thanks Mihai for the info.
I don't know why Windows 8.1 was suddenly only supporting ssh-ed25519 and
failing to connect to my Linux Mint session with that "kex error". What is
even stranger: the problem suddenly went away and I could once again use the
x2go client to connect to that session (the same session that I've had running
for more than a month - maybe two months by now). At least for now the "kex
error" is gone with the X2GO client.
Thanks for explaining why Pyhoca was working. It is good to know that both
clients use different ssh libraries in case this problem strikes again.
From: Mihai Moldovan <[email protected]>
To: [email protected]; "[email protected]" <[email protected]>
Sent: Thursday, February 23, 2017 5:35 AM
Subject: Re: [X2Go-User] X2Go Client: Kex error : no match for method server
host key alog: server [ssh-rsa], client [ssh-ed25519]
On 14.02.2017 07:30 PM, [email protected] wrote:
> Kex error : no match for method server host key alog: server [ssh-rsa], client
> [ssh-ed25519].
This is odd. Karl's suggestion won't help, as this is not related to kex
algorithms.
Instead, your server provides an RSA host key, but the client (in this case
libssh for X2Go Client) seems to support ssh-ed25519 only.
Odd, because libssh certainly does support RSA keys. Did you generate the server
host keys yourself? Maybe it's too big?
libssh definitely supports RSA keys and it should report that its list as well.
---
You're not seeing this issue with PyHoca, because PyHoca uses Paramiko, an
implementation of SSH in python. The supported features differ based upon the
implementation, as you can see (libssh vs. Paramiko in this case.)
Mihai
_______________________________________________
x2go-user mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-user
