** Description changed:
+ [Test case]
+ Connect to a x2go server on a session that has file sharing or
audo-forwarding enabled -> Error message "SCP: Warning: status code 1 received:
scp: ~<user>/.x2go/ssh: No such file or directory" needs to be clicked away
with "ok".
+
+ [Regression potential]
+ Very low as the patch removes "~<user>" from the ssh string which is the same
as just using no path spec (":") as the default is the home dir of the logged
in remote user.
+
+ --------------------------------------------------------------------------
+
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.
+ 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856795
Title:
[SRU] X2Go Client broken by libssh CVE-2019-14889 fix
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
