@pjds this bug is closed, and also I see no failure on my focal system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To m
Seeing this bug again on a Focal -> Focal system sshuttle 0.78.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage n
This bug was fixed in the package sshuttle - 0.76-1ubuntu1.2
---
sshuttle (0.76-1ubuntu1.2) xenial; urgency=medium
* d/p/lp1897987-Backward-compatibility-with-Python-2.4-server.patch:
- Fix compatibility with remote py3.4 (LP: #1897987)
* d/p/lp1897961-Fix-shell-quoting.patch:
root@sshuttle-x:~# dpkg -l | grep sshuttle
ii sshuttle 0.76-1ubuntu1
all Transparent proxy server for VPN over SSH
root@sshuttle-x:~# sshuttle --python python3 -r sshuttle-g.lxd 1.2.3.4/24
assembler.py:3: DeprecationWarning: the imp mo
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
This bug was fixed in the package sshuttle - 0.78.5-1ubuntu1.1
---
sshuttle (0.78.5-1ubuntu1.1) focal; urgency=medium
* d/p/lp1873368/0001-allow-Mux-flush-fill-to-work-with-python-3.5.patch,
d/p/lp1873368/0002-Fix-python2-server-compatibility.patch:
- fix interoperability wi
Hello Dan, or anyone else affected,
Accepted sshuttle into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sshuttle/0.76-1ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
root@lp1896299-f:~# dpkg -l|grep sshuttle
ii sshuttle 0.78.5-1 all
Transparent proxy server for VPN over SSH
root@lp1896299-f:~# sshuttle -r lp1896299-f.lxd 1.2.3.4/24
The authenticity of host 'lp1896299-f.lxd (10.202.51.43)' can't be esta
root@lp1896299-b:~# dpkg -l|grep sshuttle
ii sshuttle 0.78.3-1ubuntu1 all
Transparent proxy server for VPN over SSH
root@lp1896299-b:~# sshuttle --python python3 -r lp1896299-f.lxd 1.2.3.4/24
assembler.py:3: DeprecationWarning: the imp module i
root@lp1896299-x:~# dpkg -l|grep sshuttle
ii sshuttle 0.76-1ubuntu1
all Transparent proxy server for VPN over SSH
root@lp1896299-x:~# sshuttle --python python3 -r lp1896299-g.lxd 1.2.3.4/24
assembler.py:3: DeprecationWarning: the imp
Hello Dan, or anyone else affected,
Accepted sshuttle into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sshuttle/0.78.3-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Dan, or anyone else affected,
Accepted sshuttle into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/sshuttle/0.78.5-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
uploaded fixed versions for x/b/f as well as creating an autopkgtest to check
inter-release operation, added starting in groovy:
https://autopkgtest.ubuntu.com/packages/sshuttle
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
This bug was fixed in the package sshuttle - 1.0.4-1ubuntu1
---
sshuttle (1.0.4-1ubuntu1) groovy; urgency=medium
* d/p/lp1873368/0001-Fix-python2-server-compatibility.patch,
d/p/lp1873368/0002-Fix-flake8-line-too-long.patch,
d/p/lp1873368/0003-Fix-python2-client-compatibilit
uploaded to x/b/f/g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug go to:
https://bu
Looks like the g failures to py2 remote is fixed upstream by
c12d2ba5c6d0c7287b1e316fec4f9c9bff63c328, so I think we're almost at the
happy place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Note that the t/x failures are *not* regressions related to this bug;
they already failed with the existing versions in -release or -updates.
FROM trusty:
FAILS to python3 in t/x/b/f/g
FROM xenial:
FAILS to python3 in t
As t is ESM only now, I'm going to just ignore its failure connecting to
any
The failure from t/x->f with python2, and x->f with python3, is due to
the net-tools package not being installed by default in focal (sshuttle
fails trying to remotely run 'netstat'), while it IS installed by
default in t/x/b/g. Not sure if that's an error that should be corrected
or not.
In any c
Failure detail:
FROM trusty TO focal python2:
Traceback (most recent call last):
File "", line 1, in
File "assembler.py", line 26, in
File "server.py", line 170, in main
File "server.py", line 71, in list_routes
File "server.py", line 51, in _list_routes
File "ssubprocess.py", line 6
Sorry the last entry in that table should be FROM *groovy* not focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To man
To follow up, with my test builds from comment 36:
FROM trusty:
WORKS TO python2 in t/x/b/g
FAILS to python2 in f
FAILS to python3 in t/x/b/f/g
FROM xenial:
WORKS TO python2 in t/x/b/g
FAILS to python2 in f
FAILS to python3 in t/f
WORKS TO python3 in x/b/g
FROM bionic:
WORKS TO python2 in t/x/b/
My test builds include the patch from:
https://github.com/sshuttle/sshuttle/pull/507#
This upstream bug may still apply:
https://github.com/sshuttle/sshuttle/issues/508
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
So, what's actually happening here? My understanding of the current state is
that:
1) sshuttle 0.78.5-1ubuntu1 in focal-proposed introduces a regression in
connecting to trusty hosts
2) There's a patch merged upstream which fixes that regression
3) There's a desire for an explicit policy on when
** Changed in: sshuttle
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notific
i have test pkgs in
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1873368
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
> I don't think the upstream fix for this is actually complete
this seems to only be an issue in bionic and just requires upstream
commit 0dba8a8beb5e2a6f16042421455004c2e7587ed4 to simply ignore the
failure.
I'm still concerned about upstream's casual use of stdin/stdout fd in
place of sockets,
I don't think the upstream fix for this is actually complete; MuxWrapper
passes the files up to the SockWrapper constructor, but SockWrapper
still thinks they are sockets and uses them as such, e.g. when calling
self.rsock.setblocking(False) which will fail when SockWrapper.rsock is
a file, not a s
** Changed in: sshuttle (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: sshuttle (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
** Description changed:
[Impact]
- Endpoints that have been updated with python 3.8 seem to cause issues
- with sshuttle.
+ sshuttle fails to connect to a remote system with python >= 3.8, or
+ (after initial patch) to remote system with python <= 3.4.
[Test Case]
- Client
- $ python3
** Changed in: sshuttle
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notification
https://github.com/sshuttle/sshuttle/issues/503
** Bug watch added: github.com/sshuttle/sshuttle/issues #503
https://github.com/sshuttle/sshuttle/issues/503
** Also affects: sshuttle via
https://github.com/sshuttle/sshuttle/issues/503
Importance: Unknown
Status: Unknown
--
You r
@Eric, William,
I think you're taking a very narrow view on this when a more thoughtful
review is needed.
Ubuntu should identify a general policy on 'client <-> server' version
backwards and forwards compatibility guarantees. That policy should be
implemented here. The fact this particular clie
IMO, we should not assume that upstream cared or not about py < 3.5.
As William and I pointed out, we will most likely have to carry the patch to
future release due to ESM.
I think that opening the discussion upstream to get their official
position on this might be insightful, and then we can se
IMO we should carry it until trusty ESM expires. There are still trusty
systems around, and groovy users who need to connect to those trusty
systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18733
@Eric,
Well... We'd only be carring the change for 20.04. I would not suggest to
carry it for 20.10 or beyond. As my change is right now I dont' think I would
accept it for upstream. It should be sufficient for a stable release though.
I really suspect that if upstream cared about python < 3.
@scott,
Would it be worth submitting it upstream for them to stay backward
compatible within the python3 series ?
That way we won't have to carry the patch over and over, if this become
part of the upstream code.
- Eric
--
You received this bug notification because you are a member of Ubuntu
B
@all,
Please review a MP at
https://code.launchpad.net/~smoser/ubuntu/+source/sshuttle/+git/sshuttle/+merge/388062
that will fix this for focal -> trusty and keep focal -> focal working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Lukasz
sshuttle does not require itself to be installed on the server. Rather
it "pushes" itself from the client to the server. So the code that
executes on client is the same as that on the server.
Maybe the table below will help:
client | server | comment
trusty | focal | broken due to py3
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/sshuttle/+git/sshuttle/+merge/388062
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fai
Hey! So I guess I'd like to know a bit more before we proceed. Since
generally I do not like introducing regressions from previous behavior,
but I would first like to understand a bit more the use-case that is now
broken by this SRU.
@wgrant could you give us a bit more of an info which case in fo
I wrote to sil2100 (SRU verification team member)
He'll take a look at it when time permit, and he should update the bug
anytime soon with his 2 cents about the current situation.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
@William,
The fix here does break python < 3.5 (as advertised in the
debian/patches/ patch). It is mostly trivial to make this change in a
backwards compatible way, so we should probably do that.
I wonder what the official policy is on breaking this "client"s
interaction with an ubuntu release ve
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug
This breaks connecting to Python 3.4 hosts, e.g. trusty:
client: Connected.
Traceback (most recent call last):
File "", line 1, in
File "assembler.py", line 39, in
File "sshuttle.server", line 400, in main
File "sshuttle.ssnet", line 598, in runonce
File "sshuttle.ssnet", line 488, in
Thanks Chris ! Will ping SRU team to release it sometime this or next
week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
Prior to updating:
$ sshuttle -r sts-bastion 10.5.0.0/16
assembler.py:3: DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
client: Connected.
Traceback (most recent call last):
File "", line 1, in
File "assembler.py",
I am not super happy with the version number chosen, since we have
0.78.5-1 in both focal and eoan, but then again eoan is going EOL (in
theory) today, so I'll accept it as-is.
** Changed in: sshuttle (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed ve
** Description changed:
[Impact]
Endpoints that have been updated with python 3.8 seem to cause issues
with sshuttle.
[Test Case]
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
$
** Tags removed: sts-sponsor-slashd
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notificatio
[sts-sponsor]
Thanks for your contribution Felipe.
The debdiff has been sponsored with the following minor changes:
- Renamed the quilt patch to "d/p/0001-compatibility-with-python38.patch"
- Removed the py2 build dependencies as they are no longer used and prevent to
build properly
(python-py
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug go
@Felipe,
Two things I think should be changed in your debdiff:
a.) version should be 0.78.5-1ubuntu0.1 instead of 0.78.5-1ubuntu1 per
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging .
I'm not certain on that though.
b.) the referenced commit (9c873579) is not the co
Attaching debdiff for focal that contains a backport of commit
https://github.com/sshuttle/sshuttle/commit/9c873579348e3308123d1bf2a917b0c2f82b9dae
** Patch added: "lp1873368_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+attachment/5392645/+files/lp1873368_foc
** Changed in: sshuttle (Ubuntu Focal)
Assignee: Dan Hill (hillpd) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoi
** Description changed:
+ [Impact]
+
+ [Test Case]
+
+ [Regression Potential]
+
+ [Other Info]
+
+ [Original Description]
+
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
- $ apt-cache policy
@freyes
Do you have your focal debdiff handy still ?
I'll be happy to sponsor the work you did for sshuttle focal.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle se
Next step is to introduce the fix through SRU into sshuttle version
"0.78.5-1".
** Changed in: sshuttle (Ubuntu Groovy)
Assignee: Dan Hill (hillpd) => (unassigned)
** Changed in: sshuttle (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because y
[Groovy]
# Launchpad
https://launchpad.net/ubuntu/+source/sshuttle
# rmadison
sshuttle | 1.0.3-1 | groovy/universe | source, all
# changelog
sshuttle (1.0.3-1) unstable; urgency=medium
[ Brian May ]
* Update to latest upstream version. Closes: #953621.
* Upstream has drop
** Changed in: sshuttle (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To
@smoser,
Not for focal, but for the active development release and debian
unstable I suggest we bump to 1.0.2.
As part of the SRU, just cherry-pick the desired fix.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
@slashd,
Are you suggesting your 'A' (version 1.0.2) for focal? Unless there are
other reasons than this bug, that feels like not the right path for SRU.
So that means 'B' is the path forward for focal. So I might suggest
just doing 'B' for groovy now (adding ubuntu delta). That would then
all
** Changed in: sshuttle (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To mana
I wrote to the debian maitainer which also seems to be the author of the
desired upstream patch.
Please see debbugs #953621
I offered him 2 options
* (A) Bump "sshuttle" to upstream release "1.0.2" and take benefit of
that to modernize the package to a let's say more modern dh compat
version, ..
I created a ppa that contains the backported patch in case anyone wants
to test it - https://launchpad.net/~freyes/+archive/ubuntu/lp1873368
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title
Here's my recommendation
Let's bump Debian unstable to the version which contains the fix
upstream (which seems to be v1.0.1)
Then let's sync groovy from Debian to be on the same version (Taking
benefit of the development cycle to bump the version is best)
Then let's cherry-pick the commit into
** Changed in: sshuttle (Ubuntu Focal)
Assignee: (unassigned) => Dan Hill (hillpd)
** Changed in: sshuttle (Ubuntu Groovy)
Assignee: (unassigned) => Dan Hill (hillpd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
This is fixed by pr#431 [0], which landed in v1.0.1.
[0] https://github.com/sshuttle/sshuttle/pull/431
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect
RHEL 7.7 packages python 3.6. That's why it works.
If the host is running python 3.8+, then you have to work around this
issue by pointing to a different version of python that's available on
the host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I found an upstream bug and added details to that. If I point to
python2, client 20.04 and target 20.04 works. If I do NOT point sshuttle
to python2, but keep it at python3 it fails.
Keeping client at python3 while target is RHEL 7.7 works. Please see my
post in this upstream bug:
https://github.
I did attempt to use "sudo pip3 install sshuttle" after "apt purge
sshuttle" with the same issue.
For me, this started happening when I upgraded my target server to
20.04. I did keep the sshd_config file the same. Not sure what that
means. Let me know if I can provide any info on that.
Additional
** Changed in: sshuttle (Ubuntu)
Status: New => Confirmed
** Also affects: sshuttle (Ubuntu Groovy)
Importance: High
Status: Confirmed
** Also affects: sshuttle (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: sshuttle (Ubuntu Focal)
Status: New =
** Changed in: sshuttle (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage
Not ideal - but if the remote system has multiple versions of python, you can
work around it with:
sshuttle --python=/usr/bin/python3.7 -r ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Tit
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug go to:
https://bug
The python docs [0] indicate that the file descriptor should be a socket:
"The file descriptor should refer to a socket, but this is not checked —
subsequent operations on the object may fail if the file descriptor is invalid."
The docs do need to be corrected. bpo#35415 now explicitly checks fd
75 matches
Mail list logo
