group.of.nepali.translators team mailing list archive

[Dan Streetman <1592853@xxxxxxxxxxxxxxxxxx>]

** Summary changed:

- sshuttle doesn't support python 3.5
+ sshuttle doesn't autodetect python3 instead of 'python'

** Description changed:

+ [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

** Also affects: sshuttle (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: sshuttle (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: sshuttle (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: sshuttle (Ubuntu Bionic)
       Status: New => In Progress

** Changed in: sshuttle (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: sshuttle (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: sshuttle (Ubuntu Xenial)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: sshuttle (Ubuntu Bionic)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: sshuttle (Ubuntu)
       Status: Confirmed => 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:
  In Progress
Status in sshuttle source package in Bionic:
  In Progress

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