Bug#810930: Fixed in 0.76-1

Thank you

Bug#810930: sshuttle: Crashes if using the --seed-hosts option

Package: sshuttle Version: 0.75-1 Severity: normal Tags: patch upstream Dear Maintainer, When using the --seed-hosts command line option, sshuttle crashes on connect. This is due to difference in handling of bytes in between python 2 & 3. I submitted pull request #63 to upstream. -- System Infor

Bug#790894: More info

This is now fixed in upstream (Issue #12, pull request #13, merged in d70b5f2b89e593506834cf8ea10785d96c801dfc). On Sun, Jul 5, 2015 at 11:52 AM Shai Ayal wrote: > Thanks for looking at this. > I tried to look at upstream, but they don;t have a bug tracker on their > github page.

Bug#790894: More info

confirmed > thanks > > On Thu, Jul 02, 2015 at 07:30:57PM +, Shai Ayal wrote: > > Further investigation turns out that this error only happens when using > the > > -N, --auto-nets > > command line option. If connecting without this option (which forces > > manually

Bug#790894: More info

Further investigation turns out that this error only happens when using the -N, --auto-nets command line option. If connecting without this option (which forces manually specifying the list of subnets to route over the VPN) sshuttle works Shai

Bug#790894: sshuttle does not connect and exits with error "fatal: firewall: expected route but got ''"

Package: sshuttle Version: 0.70-1 Severity: important Dear Maintainer, After upgrade to 0.70-1, I cannot connect with sshuttle. After ssh ngotiations it fails with "fatal: firewall: expected route but got ''" This seems like an upstrream problem, but I'm not sure. Example trying to connect to

Bug#790893: sshuttle fails with "can't open file '/usr/sbin/main.py'..."

Package: sshuttle Version: 0.70-1 Severity: grave Justification: renders package unusable Dear Maintainer, After update to 0.70-1, /usr/sbin/sshuttle no longer works and exits with the error: python2: can't open file '/usr/sbin/main.py': [Errno 2] No such file or directory looking at /usr/sbin