The recent CVE fix broke SCP support in libssh, which X2Go Client (x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status code 1 received: scp: ~username/.x2go/ssh: No such file or directory\n". (Also note the literal "\n" there, but I guess we don't really need to care about that.)
The previous version worked fine and rolling the libssh4 package back fixes this issue, but also leaves users vulnerable to the fixed security issue in its scp implementation.
I've been looking at the debdiff, but spotting the actual changes is very difficult due to the reformatting that was done at the same time. This degraded the patch(es) into one big blob.
The recent CVE fix broke SCP support in libssh, which X2Go Client (x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status code 1 received: scp: ~username/ .x2go/ssh: No such file or directory\n". (Also note the literal "\n" there, but I guess we don't really need to care about that.)
The previous version worked fine and rolling the libssh4 package back fixes this issue, but also leaves users vulnerable to the fixed security issue in its scp implementation.
I've been looking at the debdiff, but spotting the actual changes is very difficult due to the reformatting that was done at the same time. This degraded the patch(es) into one big blob.