I was attempting to use x2go for the first time and ran into the issue where I already had made an existing connection to my target machine using a current OpenSSH connection.  This creates the existing default ecdsa certificate in the known_hosts file and somehow breaks x2go.  I found a few posts on how to fix this at <a href="http://john.wesorick.com/2011/11/issues-installing-x2go.html">http://john.wesorick.com/2011/11/issues-installing-x2go.html</a> and <a href="https://lists.berlios.de/pipermail/x2go-user/2011-October/000448.html">https://lists.berlios.de/pipermail/x2go-user/2011-October/000448.html</a>, but my question is why doesn&#39;t x2go support any certificate type that the underlying SSH client supports?  Or why can&#39;t it just request the other type of connection and then offer to store the new key?<div>
<br></div><div>Also I didn&#39;t see a bug section on your website so I&#39;m not sure who best to send this to, but the related error dialog needs some clean up.  The title has &quot;Authentification&quot; which I&#39;ve never heard of before.  I&#39;d assume it should be &quot;Authentication&quot;.  And the text inside the dialog has a number of spaces missing that make it look odd.  Some that should be between words, and others between words and punctuation.  If I knew where to look I&#39;d be happy to edit the source file and pass along the fixed version to someone who knew how to submit it properly.</div>
<div><br></div><div>Thanks for your time,</div><div>Joe</div>