just a final note on this, sshuttle from trusty is still affected by
this, and since focal does not install the 'net-tools' package (which
provides netstat) by default, sshuttle from trusty to a default install
of focal will fail.
** Description changed:
[impact]
the remote system sshuttle connects to must have netstat installed, or
sshuttle fails
[test case]
from a xenial system, install sshuttle and attempt to create a sshuttle
connection to a remote system that does not have netstat installed
[regression potential]
any regression would likely result in a failure to successfully
create/initialize the sshuttle connection. it is unlikely any regression
would cause problems after the tunnel is established.
[scope]
this is needed only for xenial.
this is fixed upstream with commit
809fad537fa6977da3e3915f5a125e2a3d163254 which is included in v0.78.3
and later, so this is already fixed in bionic and later.
+
+ note this bug does affect sshuttle in trusty, but that release is out of
+ standard support and into ESM only, so will not be patched (unless the
+ security team wishes to patch it in the ESM repository).
** Also affects: sshuttle (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: sshuttle (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1896299
Title:
remote requires netstat installed
Status in sshuttle package in Ubuntu:
Fix Released
Status in sshuttle source package in Trusty:
Won't Fix
Status in sshuttle source package in Xenial:
Fix Committed
Bug description:
[impact]
the remote system sshuttle connects to must have netstat installed, or
sshuttle fails
[test case]
from a xenial system, install sshuttle and attempt to create a
sshuttle connection to a remote system that does not have netstat
installed
[regression potential]
any regression would likely result in a failure to successfully
create/initialize the sshuttle connection. it is unlikely any
regression would cause problems after the tunnel is established.
[scope]
this is needed only for xenial.
this is fixed upstream with commit
809fad537fa6977da3e3915f5a125e2a3d163254 which is included in v0.78.3
and later, so this is already fixed in bionic and later.
note this bug does affect sshuttle in trusty, but that release is out
of standard support and into ESM only, so will not be patched (unless
the security team wishes to patch it in the ESM repository).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1896299/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
