<div dir="ltr"><div>Hans,</div><div>I wonder if this is the same issue that is described in bug report #1520 (<a href="https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1520">https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1520</a>). Can you try the workaround from that bug report?</div><div><br></div><div>Thanks,</div><div>Adam<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 25, 2021 at 6:03 AM Hans Peter Verne <<a href="mailto:h.p.verne@geo.uio.no">h.p.verne@geo.uio.no</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Package: x2goclient<br>
Version: 4.1.2.2<br>
<br>
Hello, devs!<br>
<br>
I'm afraid this is not a very precise bug report. Any assistance in<br>
how to investigate this is appreciated.<br>
<br>
We're running x2goclient 4.1.2.2 on Windows-10 machines, this has served<br>
us well up to now. With our new RedHat Enterprise Server 8.4 in production,<br>
we see the client crashing very often.<br>
<br>
When the client crashes, it does so shortly after trying to log in to a<br>
new or existing session. The clients "show details" window pane is activated, <br>
but the client dies before anything can be seen there.<br>
<br>
On the server, just these entries in the system logs appears:<br>
<br>
Aug 05 14:42:56 <a href="http://mimi.uio.no" rel="noreferrer" target="_blank">mimi.uio.no</a> sshd[2421324]: Connection from 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 on 2001:700:100:118::101 port 22<br>
Aug 05 14:42:59 <a href="http://mimi.uio.no" rel="noreferrer" target="_blank">mimi.uio.no</a> sshd[2421324]: Connection reset by 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 [preauth]<br>
<br>
If I disable IPv6:<br>
<br>
Aug 05 14:45:30 <a href="http://mimi.uio.no" rel="noreferrer" target="_blank">mimi.uio.no</a> sshd[2421601]: Connection from 193.157.161.44 port 57619 on 129.240.118.101 port 22<br>
Aug 05 14:45:33 <a href="http://mimi.uio.no" rel="noreferrer" target="_blank">mimi.uio.no</a> sshd[2421601]: Connection reset by 193.157.161.44 port 57619 [preauth]<br>
<br>
Note the absence of the "Fail password for ..." log entry. It looks like<br>
it never gets to even try authenticating.<br>
<br>
There is no problem logging in with putty from the same client machine,<br>
both with IPv6 and IPv4. Neither have I had this problem (at least<br>
not so frequent) with the Linux client.<br>
<br>
The server is running sshd and x2goserver from the RHEL8/EPEL repos,<br>
packages openssh-server-8.0p1-6 and x2goserver-4.1.0.3-9, respectively.<br>
<br>
I eventually tried to run sshd -ddd on the server and catch the output. <br>
The typescripts are attached (slightly edited): one where the client crashed;<br>
and one where it didn't (but couldn't authenticate, bad password). I'm no<br>
expert on ssh, but it seems like the difference appears after the key exchange<br>
("KEX done"), when the instance that crashed never reaches the bit with <br>
userauth-request.<br>
<br>
I also tried "setenforce 0" on the server, i.e. disable SELinux, but the<br>
client still crashed.<br>
<br>
As it is, I can't clearly provide a procedure to reproduce the problem,<br>
as it doesn't always happen. <br>
<br>
If more information is required, or there are suggested steps to take,<br>
please let me know.<br>
<br>
<br>
Thanks in advance, and best regards,<br>
-- <br>
Hans Peter Verne -- IT-drift Geofag.<br>
<br>
In 1934, Van der Lubbe was beheaded in a German prison yard. In 1967, a court<br>
in West Berlin overturned the 1933 verdict, and posthumously changed Van der<br>
Lubbe's sentence to eight years in prison. -- "Reichstag fire" on Wikipedia.<br>
_______________________________________________<br>
x2go-dev mailing list<br>
<a href="mailto:x2go-dev@lists.x2go.org" target="_blank">x2go-dev@lists.x2go.org</a><br>
<a href="https://lists.x2go.org/listinfo/x2go-dev" rel="noreferrer" target="_blank">https://lists.x2go.org/listinfo/x2go-dev</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Adam Dorsey<br>NOAA RDHPCS Systems Administrator Site Lead<br>CSRA / RedLine Performance Solutions, LLC<br><br>NOAA NESCC<br>1000 Galliher Drive, Suite 333, Fairmont, WV 26554<br>office: (304) 367-2882<br>cell: (304) 685-9345<br><a href="mailto:adam.dorsey@noaa.gov" target="_blank">adam.dorsey@noaa.gov</a><br></div></div></div></div></div></div>