<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1487894130603_12226"><span id="yui_3_16_0_1_1487894130603_12250">Thanks Mihai for the info.</span></div><div id="yui_3_16_0_1_1487894130603_12266"><span id="yui_3_16_0_1_1487894130603_12250"><br></span></div><div dir="ltr" id="yui_3_16_0_1_1487894130603_12437"><span id="yui_3_16_0_1_1487894130603_12250">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). </span><span id="yui_3_16_0_1_1487894130603_12250">At least for now the "kex error" is gone with the X2GO client. <br></span></div><div dir="ltr" id="yui_3_16_0_1_1487894130603_12467"><span id="yui_3_16_0_1_1487894130603_12250"><br></span></div><div dir="ltr" id="yui_3_16_0_1_1487894130603_12501"><span id="yui_3_16_0_1_1487894130603_12250">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.</span></div><br><div class="qtdSeparateBR" id="yui_3_16_0_1_1487894130603_12236"><br></div><div class="yahoo_quoted" id="yui_3_16_0_1_1487894130603_12240" style="display: block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1487894130603_12239"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1487894130603_12238"> <div dir="ltr" id="yui_3_16_0_1_1487894130603_12237"> <font id="yui_3_16_0_1_1487894130603_12242" size="2" face="Arial"> <hr id="yui_3_16_0_1_1487894130603_12241" size="1"> <b><span style="font-weight:bold;">From:</span></b> Mihai Moldovan <ionic@ionic.de><br> <b><span style="font-weight: bold;">To:</span></b> jmmec2014@yahoo.com; "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, February 23, 2017 5:35 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [X2Go-User] X2Go Client: Kex error : no match for method server host key alog: server [ssh-rsa], client [ssh-ed25519]<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_1_1487894130603_12243"><br>On 14.02.2017 07:30 PM, <a shape="rect" ymailto="mailto:jmmec2014@yahoo.com" href="mailto:jmmec2014@yahoo.com" id="yui_3_16_0_1_1487894130603_12388">jmmec2014@yahoo.com</a> wrote:<div class="yqt6393220816" id="yqtfd78145"><br clear="none">> Kex error : no match for method server host key alog: server [ssh-rsa], client<br clear="none">> [ssh-ed25519].</div><br clear="none"><br clear="none">This is odd. Karl's suggestion won't help, as this is not related to kex algorithms.<br clear="none"><br clear="none">Instead, your server provides an RSA host key, but the client (in this case<br clear="none">libssh for X2Go Client) seems to support ssh-ed25519 only.<br clear="none"><br clear="none">Odd, because libssh certainly does support RSA keys. Did you generate the server<br clear="none">host keys yourself? Maybe it's too big?<br clear="none"><br clear="none">libssh definitely supports RSA keys and it should report that its list as well.<br clear="none"><br clear="none"><br clear="none">---<br clear="none"><br clear="none">You're not seeing this issue with PyHoca, because PyHoca uses Paramiko, an<br clear="none">implementation of SSH in python. The supported features differ based upon the<br clear="none">implementation, as you can see (libssh vs. Paramiko in this case.)<br clear="none"><br clear="none"><br clear="none"><br clear="none">Mihai<div class="yqt6393220816" id="yqtfd40748"><br clear="none"><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>