#922 - Avoiding X2GO Servers all using the same SSH_PORT - what conflicts when try to connect to different servers from one windows terminal (multiple sessions of x2go client)

X2Go Bug report logs - #922
Avoiding X2GO Servers all using the same SSH_PORT - what conflicts when try to connect to different servers from one windows terminal (multiple sessions of x2go client)

Reported by: Robert Nowotny <rnowotny@rotek.at>

Date: Mon, 17 Aug 2015 14:05:02 UTC

Severity: normal

Tags: pending

Found in version 4.0.1.19

Fixed in version 4.0.1.20

Done: X2Go Release Manager <git-admin@x2go.org>

Bug is archived. No further changes may be made.

Received: (at 922) by bugs.x2go.org; 30 Dec 2015 10:04:01 +0000
From X2Go-ML-1@baur-itcs.de  Wed Dec 30 11:04:00 2015
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,URIBL_BLOCKED
	autolearn=ham version=3.3.2
Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 63B203C574
	for <922@bugs.x2go.org>; Wed, 30 Dec 2015 11:04:00 +0100 (CET)
Received: from [192.168.0.171] ([109.192.26.232]) by mrelayeu.kundenserver.de
 (mreue101) with ESMTPSA (Nemesis) id 0MX0aK-1akAZ31qdw-00VuJC for
 <922@bugs.x2go.org>; Wed, 30 Dec 2015 10:51:29 +0100
Subject: Fwd: Re: [X2Go-Dev] X2Go Server contains some IPv4/non-IPv6 logic for
 creating ports.
References: <20151230094019.Horde.BvXKCVdhCeBQzxghEriSPCL@mail.das-netzwerkteam.de>
To: 922@bugs.x2go.org
From: Stefan Baur <X2Go-ML-1@baur-itcs.de>
X-Forwarded-Message-Id: <20151230094019.Horde.BvXKCVdhCeBQzxghEriSPCL@mail.das-netzwerkteam.de>
Message-ID: <5683A920.4000608@baur-itcs.de>
Date: Wed, 30 Dec 2015 10:51:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <20151230094019.Horde.BvXKCVdhCeBQzxghEriSPCL@mail.das-netzwerkteam.de>
Content-Type: multipart/mixed;
 boundary="------------070105030704030902080809"
X-Provags-ID: V03:K0:Z1G9MVC/QD9gwAjpBHt37460/9RbHNDBG8DAHLGgK1/wV4U5zcB
 6JBvvK6kXBjY8mu6YJ2/C6Vd3swz1H28Lt5Z0f54lr5QrC6t9EUTWZDHpTxCMuI/qLfsfMC
 CMvM1fEeLH/14LITH3yBdx5IOIwTRiA8rO0dC+0NY0f2xSs1fnNIfiEQy8Oxpjz1qDUC3Ry
 ctgEiXNsEVcd5zalPaeMw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:WbDtuLZ05gM=:qG00oPTwcIbwzwwBw/wZPm
 +PqH4jUhIzpUn3EI6AzTumsX1+4elpVyXjZcj/IlLqL7/9QkvYDNOXs7KUr3VCtozQim38eCK
 sNfjNLiVbafQmc2t4LMgAffsszQcZE8g8TSIdYo4lDAqolzyX7Z9h0R7yfY1FbI9+3NKKghDU
 Pt2sbQahWaQeF50BPuh56/LsZEA9LVgDZn0qe34nO6qMGNGWdSNI/lldkiiwq/eJ9JjJGHfRl
 mB1JX6m8Rudk/SPjx1NVm0qN60K7Vjd2Z2kULO2NPui4qrdBEsvVo0PAcKiudKdjE8c8iXjDJ
 kE3pMnN5Zm1Y63BHJxJlSPkI1GQkcOwyVV/c6flF6goQx2nmLo6R2l2TpJq9DXShXwgEx2E51
 qV3YHvW/8vw2tW9JQmYib+5xU0TQfVg/f8pXOC32XifSadaTmRLWxX0ng8F2fyqVeyroqigzl
 N+7HbN+Djo2TxwKu9FVjjQ0re3duNQ73d0XlYO2nJcqxRuzt4e22JQ/IhrbsubZVyvrZqTK0i
 Bz2zwvH9mL8w5lDx5rLdqH63+4eL5V4jVIGdCvh14y6LoKpf6urI8ljvm8VAenerlxtlKv6zw
 RlLDzM2yYRQIkH3ZAZsN6rFe4HFgAkgw47nVjQ7ux55rsq8s7wjhgfhApaK6pdV4G5EKpUWaA
 geoZvkQKVSlin6NQViKCDlYvwIxyRPkRmvyATiqLvVO/NL1Bcr7G1AHNBI2vjaORFHWQ=

[Message part 1 (text/plain, inline)]

Forwarding this to the bugtracker so it doesn't get lost ... -------- Weitergeleitete Nachricht -------- Betreff: Re: [X2Go-Dev] X2Go Server contains some IPv4/non-IPv6 logic for creating ports. Datum: Wed, 30 Dec 2015 09:40:19 +0000 Von: Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Organisation: DAS-NETZWERKTEAM An: x2go-dev@lists.x2go.org Furthermore... On Mi 30 Dez 2015 10:21:20 CET, Mike Gabriel wrote: >> +get_server_ip_address() { >> + # The provided IP address should be outside of any local network. >> + # We are only interested in how the kernel would try to reach the >> + # non-local IP address specified here. It is not actually contacted >> + # in any way. >> + typeset ip_output="$(ip route get 8.8.8.8)" Since when does X2Go promote Google??? Or even depend on them? As this patch is IPv6-flawed anyway, the next request is pointless... In case the patch is kept, please make this configurable and use the IP address of japsand.x2go.org or some other static IP on the internet that is more political correct, please. Good candidates for this are the root DNS servers of the world: IPv4: 192.228.79.201 192.33.4.12 199.7.91.13 192.203.230.10 192.5.5.241 192.112.36.4 128.63.2.53 192.36.148.17 192.58.128.30 193.0.14.129 199.7.83.42 202.12.27.33 IPv6: 2001:503:ba3e::2:30 2001:500:84::b 2001:500:2::c 2001:500:2d::d 2001:500:2f::f 2001:500:1::803f:235 2001:7fe::53 2001:503:c27::2:30 2001:7fd::1 2001:500:3::42 2001:dc3::35 Regarding IPv4/IPv6 flaw in the patch... There are also setup that are IPv6 only... Tststs... Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu May 2 02:41:27 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/.

X2Go Bug report logs - #922 Avoiding X2GO Servers all using the same SSH_PORT - what conflicts when try to connect to different servers from one windows terminal (multiple sessions of x2go client)

X2Go Bug report logs - #922
Avoiding X2GO Servers all using the same SSH_PORT - what conflicts when try to connect to different servers from one windows terminal (multiple sessions of x2go client)