X2Go Bug report logs - #765
Kex Error in X2Go client

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: promox <promox@gmx.com>

Date: Sat, 24 Jan 2015 12:55:02 UTC

Severity: normal

Found in version 4.0.3.1

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#765: Workaround. And was this on Windows?
Reply-To: Michael DePaulo <mikedep333@gmail.com>, 765@bugs.x2go.org
Resent-From: Michael DePaulo <mikedep333@gmail.com>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 03 Mar 2015 13:35:02 +0000
Resent-Message-ID: <handler.765.B765.14253894302384@bugs.x2go.org>
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: <CAMKht8jdu4juOk_EFwJ7j0d1TOyHncrZS4FEp4oeO3pV07UFZg@mail.gmail.com>
From: Michael DePaulo <mikedep333@gmail.com>
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

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 15:41:08 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.