Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

@miss-islington
Copy link
Contributor

@miss-islingtonmiss-islington commentedOct 20, 2022
edited
Loading

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 commit49f6106)

Co-authored-by: Gregory P. Smithgreg@krypto.org

Automerge-Triggered-By: GH:gpshead

…ythonGH-98501)Linux abstract sockets are insecure as they lack any form of filesystempermissions so their use allows anyone on the system to inject code intothe process.This removes the default preference for abstract sockets inmultiprocessing introduced in Python 3.9+ viapython#18866 while fixingpython#84031.Explicit use of an abstract socket by a user now generates aRuntimeWarning.  If we choose to keep this warning, it should bebackported to the 3.7 and 3.8 branches.(cherry picked from commit49f6106)Co-authored-by: Gregory P. Smith <greg@krypto.org>
@miss-islingtonmiss-islington merged commiteae692e intopython:3.10Oct 20, 2022
@miss-islingtonmiss-islington deleted the backport-49f6106-3.10 branchOctober 20, 2022 23:56
fruch added a commit to fruch/scylla-cluster-tests that referenced this pull requestJul 11, 2023
looks like we are using a very early release of python 3.10and we didn't got the revert that was done inpython/cpython#98503rebuilding image with latest release of python 3.10Fixes:scylladb#6345Ref:python/cpython#98503
fruch added a commit to scylladb/scylla-cluster-tests that referenced this pull requestJul 11, 2023
looks like we are using a very early release of python 3.10and we didn't got the revert that was done inpython/cpython#98503rebuilding image with latest release of python 3.10Fixes:#6345Ref:python/cpython#98503
fruch added a commit to scylladb/scylla-cluster-tests that referenced this pull requestJul 11, 2023
looks like we are using a very early release of python 3.10and we didn't got the revert that was done inpython/cpython#98503rebuilding image with latest release of python 3.10Fixes:#6345Ref:python/cpython#98503(cherry picked from commit61bd889)
soyacz pushed a commit to soyacz/scylla-cluster-tests that referenced this pull requestMay 9, 2024
looks like we are using a very early release of python 3.10and we didn't got the revert that was done inpython/cpython#98503rebuilding image with latest release of python 3.10Fixes:scylladb#6345Ref:python/cpython#98503(cherry picked from commit61bd889)
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@gpsheadgpsheadgpshead approved these changes

@pablogsalpablogsalAwaiting requested review from pablogsal

Assignees

No one assigned

Labels

release-blockertype-bugAn unexpected behavior, bug, or errortype-securityA security issue

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@miss-islington@gpshead@bedevere-bot

[8]ページ先頭

©2009-2025 Movatter.jp