Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
[3.9] gh-97514: Don't use Linux abstract sockets for multiprocessing (GH-98501)#98504
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
Conversation
…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>
32b2d32 to85178d5CompareSorry, I can't merge this PR. Reason: |
Sorry, I can't merge this PR. Reason: |
1 similar comment
Sorry, I can't merge this PR. Reason: |
Sorry, I can't merge this PR. Reason: |
Uh oh!
There was an error while loading.Please reload this page.
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