group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1592853@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package sshuttle - 0.78.3-1ubuntu1.1

---------------
sshuttle (0.78.3-1ubuntu1.1) bionic; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1592853-Use-versions-of-python3-greater-than-3.5-when-availa.patch:
    - detect if remote python is 'python' or 'python3' (LP: #1592853)
  * d/p/lp1873368/0001-Don-t-crash-if-we-can-t-look-up-peername.patch,
    d/p/lp1873368/0002-allow-Mux-flush-fill-to-work-with-python-3.5.patch,
    d/p/lp1873368/0003-Fix-python2-server-compatibility.patch,
    - fix interoperability with other releases py2/py3
      (same LP bug as below)

  [ Felipe Reyes ]
  * d/p/0001-compatibility-with-python38.patch:
    Backport patch to make sshuttle compatible
    with python-3.8. (LP: #1873368). Closes: #953621.

 -- Felipe Reyes <felipe.reyes@xxxxxxxxxxxxx>  Sat, 19 Sep 2020 13:54:06
-0400

** Changed in: sshuttle (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
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/1592853

Title:
  sshuttle doesn't autodetect python3 instead of 'python'

Status in sshuttle package in Ubuntu:
  Fix Released
Status in sshuttle source package in Xenial:
  Fix Committed
Status in sshuttle source package in Bionic:
  Fix Released

Bug description:
  [impact]

  connecting with sshuttle to a remote system where the only version of
  python is python3 named 'python3' and no binary named 'python' fails

  [test case]

  from a x/b system, attempt to sshuttle to a remote system where only
  'python3' exists, and no 'python' binary exists

  [regression potential]

  any regression would likely cause problems with the initial sshuttle
  connection; it's unlikely any issues would be caused after the
  connection is successfully established.

  [scope]

  this is needed only in x/b.

  this appears to be fixed upstream with commit
  9b7ce2811ec3ef35b9b7f7dfc157127bc46ece47 which is included starting in
  v0.78.4, so this fixed already in focal and later.

  [original description]

  sshuttle package implementation doesn't support Python 3.5 on remote
  host running Xenial and late from a machine <= Wily release.

  This cause the connection to fail if the connection is negotiated from
  a Precise, Trusty or Wily machine and if the remote host is running
  Xenial (16.04).

  Example took from "Wily" :

  $ sshuttle -r <REMOTE_SERVER> <TARGET_REMOTE_SUBNET>/0 -vv

  Starting sshuttle proxy.
  UDP support requires tproxy; disabling UDP.
  Binding redirector: 12300 12299
  TCP redirector listening on ('127.0.0.1', 12299).
  firewall manager ready method nat.
  c : connecting to server...
  c : executing: ['ssh', '<REMOTE_SERVER>', '--', 'P=python2; $P -V 2>/dev/null || P=python; exec "$P" -c \'import sys; skip_imports=1; verbosity=2; exec compile(sys.stdin.read(770), "assembler.py", "exec")\'']
  c :  > channel=0 cmd=PING len=7 (fullness=0)

  bash: line 0: exec: python: not found
  Read line ""c : fatal: server died with error code 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1592853/+subscriptions