sshuttle on Xenial and late does support Python 3.5, include the
upstream commit :
ba1cf58 Add Python 3.5 support.
Introduced upstream in branch : v0.73~32
Eric
** Description changed:
- sshuttle package implementation doesn't support Python 3.5 on Trusty and
- Wily.
+ sshuttle package implementation doesn't support Python 3.5 on remote
+ host from system <= 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_CIDR>/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
** Description changed:
sshuttle package implementation doesn't support Python 3.5 on remote
host from system <= 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_CIDR>/0 -vv
+ $ 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
** Description changed:
sshuttle package implementation doesn't support Python 3.5 on remote
- host from system <= Wily release.
+ 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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592853
Title:
sshuttle doesn't support python 3.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1592853/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
