A quick update for this bug:
Today I tested the same scenario (Cipher aes128-ctr) on our test cluster
using the latest Windows snapshot client, version
4.1.2.3-2021.07.13-df4a8ec. The issue as described in this bug report is
still present.
Thanks,
Adam
On Fri, Mar 19, 2021 at 2:28 PM Adam
I can confirm this issue in my own environment as well. X2Go server
version is 4.1.0.3-9.el7 running on CentOS 7. Affected users are running
X2Go client version 4.1.2.2 on Windows 10 (though this may affect other
Windows versions as well).
We forced the use of the aes128-ctr cipher yesterday on
It is probably required to recompile x2goclient with a current libssh.
As a workaround you can try to build a tunnel via the jumphost with
the window ssh and connect x2goclient to that tunnel instead of using
a proxy in the x2goclient configuration.
On Thu, Jan 14, 2021 at 4:25 PM Stefan Baur
Am 14.01.21 um 08:47 schrieb marian.schwa...@dlr.de:
> 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.
Sure sounds like something that *can* be patched. If you want to
expedite patching, feel free to
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
