On 25.08.2021 15:19, Adam Dorsey - NOAA Affiliate wrote:
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?
Thank you for the feedback.
I assume the workaround would be to remove aes128-ctr from the "Ciphers" line in /etc/ssh/sshd_config
I can do that for test purpose, but it will be reset by automatic routines (CFengine) maintained by central IT, so it will be a bit more work (and I would need some arguments) to get it permanently changed.
This is, however, a smoking gun. The comment in the file says the cipher selections was revised 2021-06-22.
But when me and my coworkers test the x2go client now, it works
perfectly every time! On the same w-10 machines, with the same
server, same session config. And no changes to sshd_config.
Thus, testing without aes128-ctr would not tell me much.
Unless this is just coincidental (it didn't always crash, anyway), the only change I can imagine is some Windows update since I struggled with this 3 weeks ago.
Also, I noted that x2go complained about the host key being changed (it hasn't), with the usual warning about MITM attack (pretty sure there isn't one). So maybe some bug was fixed in a Windows library routine used for key handling? I'm throwing things at the wall here!
Bottom line, we can probably let this problem lie for now. I still wish for a way to catch diagnostics from the x2go client, also after the status pane has closed.
Regards,
Hans Peter Verne -- IT-drift Geofag.
In 1934, Van der Lubbe was beheaded in a German prison yard. In 1967, a court in West Berlin overturned the 1933 verdict, and posthumously changed Van der Lubbe's sentence to eight years in prison. -- "Reichstag fire" on Wikipedia.