From unknown Fri Mar 29 07:42:24 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#765: Workaround. And was this on Windows? Reply-To: Michael DePaulo , 765@bugs.x2go.org Resent-From: Michael DePaulo Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Tue, 03 Mar 2015 13:35:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 765 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: Received: via spool by 765-submit@bugs.x2go.org id=B765.14253894302384 (code B ref 765); Tue, 03 Mar 2015 13:35:02 +0000 Received: (at 765) by bugs.x2go.org; 3 Mar 2015 13:30:30 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM, T_DKIM_INVALID autolearn=ham version=3.3.2 Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 06C215DCA8 for <765@bugs.x2go.org>; Tue, 3 Mar 2015 14:30:30 +0100 (CET) Received: by wesq59 with SMTP id q59so2896008wes.3 for <765@bugs.x2go.org>; Tue, 03 Mar 2015 05:30:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=XasjMkU8h8meFxSJohcH426DFx1JUl6A8tIODgPhPRs=; b=m87osZrtifYmu6uRVE/2a0/sob/hfgY8c209X6zUDUB98JQ6GWxR5wGJ8xmZPmH+++ c2BfOxs26Cw8t+hknEGd1aUBaGZiE0Z6T6c0CF+buM8ftlKa9ZSx7ycIdwH3Vf4/wKeK Ykr0axCIw5M3CXZkJ7BTDcJX6BEgWgBcYA5BUaO1cj/yuuofmQu7dXRjv4QdtmFrtkYl vPZIM3T/oxbMrqrcasQiVascO4OQqlYqP6wg4JM9d2pC7CAc98+Wzrp7VmL6qcNdasye IOQphLlBSJ0e69Oi6O2Wl6pfFf4kY37Ruk0bbktUBk0tC2+VVWN0T8TtEppl+rb5jFZQ Y+rg== MIME-Version: 1.0 X-Received: by 10.194.60.173 with SMTP id i13mr68397415wjr.124.1425389429748; Tue, 03 Mar 2015 05:30:29 -0800 (PST) Received: by 10.180.80.8 with HTTP; Tue, 3 Mar 2015 05:30:29 -0800 (PST) Date: Tue, 3 Mar 2015 08:30:29 -0500 Message-ID: From: Michael DePaulo To: promox@gmx.com Cc: 765@bugs.x2go.org Content-Type: text/plain; charset=UTF-8 Hi Promox, Sorry to hear that you ran into this bug. Were you using X2Go Client for Windows? I reproduced it yesterday with X2Go Client for Windows 4.0.3.2-20150301. It appears that this occurs when the server does not have an ecdsa 256-bit key. Some Linux distros generate one by default, others do not. The workaround is to generate such a key: sudo ssh-keygen -f /etc/ssh/ssh_host_ecdsa_key -N '' -t ecdsa -b 256 I think this is a bug in terms of how x2goclient uses libssh -Mike#2