-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python27: fix CVE-2021-23336 #118403
python27: fix CVE-2021-23336 #118403
Conversation
From the archive `python-gentoo-patches-2.7.18_p8.tar.xz` found at https://dev.gentoo.org/~mgorny/dist/python/, I copied `0024-3.6-bpo-42967-only-use-as-a-query-string-separator-G.patch`.
What is the source of the patchset? Is it python/cpython#24297? Looks like https://gitweb.gentoo.org/fork/cpython.git/commit/?h=gentoo-2.7-vanilla&id=255d1d464a7f45a20986aa014c78e85ef47e6591 in fact. |
Anyway, not sure if this needs to go to staging, as we don't recurse into python27Packages for a while now. |
See the commit message. |
Nixpkgs-review listed more than 2000 packages. I guess most of these are only dependencies though. |
This is an API change. As is argued in https://bugs.python.org/issue42967, this should not have been merged into CPython (and I agree). By now, "the damage is done". It may cause some breakage with some other downstream packages. Be prepared to patch up failing packages that are still in use. I won't merge this, but won't block it either. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Be prepared to patch up failing packages that are still in use.
Python2 package are in a broken state anyway and regularly break üackages that still rely on them like nixops. Also from the issue it is not clear what will be broken.
I can confirm that nixops still builds. |
Even though I agree with @FRidh's assessment that upstream shouldn't have merged the patch, I believe that we should go with (I believe) the majority of Linux distributions and apply this patch. We don't want our users to come across an unexpected difference to other distros. |
IF the upstream merged this, can we get the upstream version then, instead of a specific distro patch? |
Upstream only applied this patch to versions of Python that are still supported. Python 2.7 is not. |
The other distros are using it. |
People keep python2.7 alive for example for NixOps. 😞 |
People keep python2.7 alive for example for NixOps. 😞
I wonder if PyPy2 is going to be supported (might be, if the engine is the same, and Python2 parsing is not exactly a thing in need of updates), and if NixOps can be simply run on PyPy2
|
Can NixOps be rewritten in Py3? |
See NixOS/nixops#1242. |
Just to make it clear: I am not saying that we will drop the Py27 files now. We will just not care for them, at least not with the same motivation as before. After all, we erase nothing from a Git repo. |
Motivation for this change
fixes #116917
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)