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
Dorsey - NOAA Affiliate <
adam.dor...@noaa.gov> wrote:
> 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
> Window
Hans,
I wonder if this is the same issue that is described in bug report #1520 (
https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1520). Can you try the
workaround from that bug report?
Thanks,
Adam
On Wed, Aug 25, 2021 at 6:03 AM Hans Peter Verne
wrote:
> Package: x2goclient
> Version:
n,
instance SshMasterConnection(0x548e2a8) created.
x2go-DEBUG-../src/sshmasterconnection.cpp:492> SshMasterConnection,
instance SshMasterConnection(0x548e2a8) entering
thread.
x2go-DEBUG-../src/sshmasterconnection.cpp:573> Setting SSH directory to
C:/Users/Adam/ssh
x2go-DEBUG-../src/sshmasterconnec
