X2Go Bug report logs - #1520
Proxy-Server - SSH - strong Cipher crash 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: <Marian.Schwarcz@dlr.de>

Date: Thu, 14 Jan 2021 07:50:02 UTC

Severity: normal

Found in version 4.1.2.2-2020.02.13

Full log

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

Received: (at submit) by bugs.x2go.org; 14 Jan 2021 07:47:38 +0000
From Marian.Schwarcz@dlr.de  Thu Jan 14 08:47:34 2021
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,HTML_MESSAGE,
	RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE autolearn=ham
	autolearn_force=no version=3.4.2
Received: from mailin.dlr.de (mailin.dlr.de [194.94.201.12])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 9BA145DAC1
	for <submit@bugs.x2go.org>; Thu, 14 Jan 2021 08:47:34 +0100 (CET)
IronPort-SDR: 4yDwW5Pt2JN6XRiW+PzvSKJmW2PC9jHddFLo3oXU8VLi+4MRwp1Xhd3OuCBA70Nl4uOfBVg3i+
 WMX1r5Fx6s8Q==
X-IPAS-Result: A2HoBABY9v9f/xeKuApigQmCcoFpFYFDlXecPwsBAQEBAQEBAQEIARMcBAEBhjsmOBMCAwEBAQMCAwEBAQEGAQEBAQEBBQQBAQKGFUWCOCKEKl4BNgFJFwEOAQQbE4MMgX6wSoE0hViFB4E4j3SBEYJrhGExYAIDhSsEglKBV2woJiNljykZimOBRopwkT8HgWiWSYNAgmcrkwiPXoJugzKCMagUhHwCBAIEBQIWgW2Be3GDOU8XAg2caoErAgYBCQEBAwmMEw+BJIERAQE
IronPort-PHdr: 9a23:bAMutR1nxSXP/spEsmDT+DRfVm0co7zxezQtwd8ZseIQKPad9pjvdHbS+e9qxAeQG9mCu7Qc16GH7+igATVGvc/e9ihaMdRlbFwssY0uhQsuAcqIWwXQDcXBSGgEJvlET0Jv5HqhMEJYS47UblzWpWCuv3ZJQk2sfQV6Kf7oFYHMks+5y/69+4HJYwVPmTGxfa5+IA+5oAnMtcQam5duJ6k+xhbNrXZDZuBayX91KV6JkBvw+8W98IR//yhMvv4q6tJNX7j9c6kkV7JTES4oM3oy5M3ltBnDSRWA634BWWgIkRRGHhbI4gjiUpj+riX1uOx92DKHPcLtVrA7RS6i76ZwRxD2jioMKiM0/3vWisx0i6JbvQ6hqhliyIPafI2ZKPxzdb7bcNgHR2ROQ9xRWjRBDI2icoUPE+QPM+VZr4bhqFQDtgGxCRWuBO711jNEmmL60Ksn2OohCwHG2wkgEsoJvXrTttr1LqYSXvqzzKXS0DvMc/NW2Dnn54jSbh8goOqBUq90ccrL00UgCh3Kg0yWpIf4MDybyv4DvHKH7+p8S+2vkWgnphlyrzWh28ohlJXFip8Rx17E9Ch0xIU4KNm3RkNlfNKpDZldui+UOodoX88uXn9ltSg+x7AbpJO2YDQHxZclyhPcbfGMbouG4gr7WeqMPTt0nm9pdbGwihqo7EStxO7xWtOq3FtEtiZJj8XAumoQ2xHQ5cWLUOZx80mi1DqVyQze6u5JLEYpnqTBMZEh2KQ/lp8LvETGGS/5hVv5gbeNdkUh5uio8+PnYqj6ppOEN497lAX+MqM2l8KxB+o2PAcAUWib9+q717Pt+lf3TKtEg/M5k6bUrorWJcUdpq6lGQ9ayJwv5Au7Dze8ytgXgGcIIEpEeBKBkYfpJ0nDLO3kAfulnlihkzhmy+rbMrDvAZjBNGbPnbn5cbZ48UFcyQ4zzd5F55JTD7EMOPX9VVXrtNzZFBA5NRa4zfv7B9V92IIRQ3iPDbOYMa7JrFCI4vgvL/ORa4ALoDr9MeQq5+byjX8lnl8QZbKp3YYMZ3C9H/RmP16UbmHxgtcOCmcGpAU/QPLliF2FSzJTYGyyX61vrg08Xda9EI3GR5yFiqGOx2GrRJJRIGdcBQbfP23vctDQfv4WaSuUZPRqkiMNT7OzY4Mlz1eiuVmpmPJcMuPI93hA5trY399v6riLmA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,346,1602540000"; 
   d="scan'208,217";a="46029359"
From: <Marian.Schwarcz@dlr.de>
To: <submit@bugs.x2go.org>
Subject: Proxy-Server - SSH - strong Cipher crash x2Go-Client
Thread-Topic: Proxy-Server - SSH - strong Cipher crash x2Go-Client
Thread-Index: AdbqSWsM7/JN+gIBSZ2CRVolZRtFrg==
Date: Thu, 14 Jan 2021 07:47:33 +0000
Message-ID: <d2a6c484573844229e9e87c588ec8ba0@dlr.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tm-snts-smtp: 9117C79BEB61111EF066BA920226D64AF5A33AF3BB9B9196A226AFC5D074B2DF2000:8
Content-Type: multipart/alternative;
	boundary="_000_d2a6c484573844229e9e87c588ec8ba0dlrde_"
MIME-Version: 1.0

[Message part 1 (text/plain, inline)]
Package: x2goClient
Version: 4.1.2.2-2020.02.13

Host-System: Windows 10, und Windows Server 2012 R2 (German Language)
Installations-Typ: Recommended (Default)

*** Problem Description ***
When using x2GoClient via jumpserver (as SSH-Proxy-Server), then is X2GoClient automatic closed (without any Information). Problem are the SSH-Strong-Ciphers, which are configured in SSHd on Jumpserver. Strong Ciphers => x2GoClient crashed. If default Ciphers => x2GoClient and connection works.

*** X2GoClient - Configuration ***
Sitzungsname: test
Pfad: /
Host: ziel-server
Login: test_ye
SSH-Port: 22

Proxy-Server für SSH-Verbindung verwenden
SSH
Host: jumpserver
Port: 22
Gleiche Anmeldung wie für X2Go-Server
Gleiches Kennwort wie für X2Go-Server

XFCE

*** Jumpserver Configuration) ***
Jumpserver SSHd Config: /etc/ssh/sshd_config  (CentOS 7)
Ciphers aes128-ctr,aes192-ctr,aes256-ctr

The ciphers are used for strong Encryption. Then access from x2GoClient via jumpserver cannot handle this.
------

When the Cipher-Restriction is not configured:
Jumpserver SSHd Confg: (CentOS 7)
#Ciphers aes128-ctr,aes192-ctr,aes256-ctr

then the connection from x2GoClient via jumpserver to Destination X2Go-Server does work.


I hope I provided all needed information for you. Let me know if this can be patched, or does our Company need to search for other solution.
Thank you.

Best regards,
Marián Schwarcz


[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 16:34:37 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.