Skip to content
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

[3.10] gh-97514: Don't use Linux abstract sockets for multiprocessing (GH-98501) #98503

Merged
merged 1 commit into from
Oct 20, 2022

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Oct 20, 2022

Linux abstract sockets are insecure as they lack any form of filesystem
permissions so their use allows anyone on the system to inject code into
the process.

This removes the default preference for abstract sockets in
multiprocessing introduced in Python 3.9+ via
#18866 while fixing
#84031.

Explicit use of an abstract socket by a user now generates a
RuntimeWarning. If we choose to keep this warning, it should be
backported to the 3.7 and 3.8 branches.
(cherry picked from commit 49f6106)

Co-authored-by: Gregory P. Smith [email protected]

Automerge-Triggered-By: GH:gpshead

…ythonGH-98501)

Linux abstract sockets are insecure as they lack any form of filesystem
permissions so their use allows anyone on the system to inject code into
the process.

This removes the default preference for abstract sockets in
multiprocessing introduced in Python 3.9+ via
python#18866 while fixing
python#84031.

Explicit use of an abstract socket by a user now generates a
RuntimeWarning.  If we choose to keep this warning, it should be
backported to the 3.7 and 3.8 branches.
(cherry picked from commit 49f6106)

Co-authored-by: Gregory P. Smith <[email protected]>
@miss-islington miss-islington merged commit eae692e into python:3.10 Oct 20, 2022
@miss-islington miss-islington deleted the backport-49f6106-3.10 branch October 20, 2022 23:56
fruch added a commit to fruch/scylla-cluster-tests that referenced this pull request Jul 11, 2023
looks like we are using a very early release of python 3.10
and we didn't got the revert that was done in python/cpython#98503
rebuilding image with latest release of python 3.10

Fixes: scylladb#6345
Ref: python/cpython#98503
fruch added a commit to scylladb/scylla-cluster-tests that referenced this pull request Jul 11, 2023
looks like we are using a very early release of python 3.10
and we didn't got the revert that was done in python/cpython#98503
rebuilding image with latest release of python 3.10

Fixes: #6345
Ref: python/cpython#98503
fruch added a commit to scylladb/scylla-cluster-tests that referenced this pull request Jul 11, 2023
looks like we are using a very early release of python 3.10
and we didn't got the revert that was done in python/cpython#98503
rebuilding image with latest release of python 3.10

Fixes: #6345
Ref: python/cpython#98503
(cherry picked from commit 61bd889)
soyacz pushed a commit to soyacz/scylla-cluster-tests that referenced this pull request May 9, 2024
looks like we are using a very early release of python 3.10
and we didn't got the revert that was done in python/cpython#98503
rebuilding image with latest release of python 3.10

Fixes: scylladb#6345
Ref: python/cpython#98503
(cherry picked from commit 61bd889)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker type-bug An unexpected behavior, bug, or error type-security A security issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants