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

bpo-39850: Add support for abstract sockets in multiprocessing#18866

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
pablogsal merged 7 commits intopython:masterfrompablogsal:bpo-39850
Mar 9, 2020

Conversation

@pablogsal
Copy link
Member

@pablogsalpablogsal commentedMar 9, 2020•
edited by bedevere-bot
Loading

Copy link
Member

@pitroupitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM, just a nit.

@pitrou
Copy link
Member

By the way, I don't think this can be backported since it's a behaviour change. If we want to fix support for abstract sockets on 3.7-3.8 we'll need a different patch.

@pablogsal
Copy link
MemberAuthor

@pitrou Would you like me to split this PR in two (one with the fix 'per se' and the other with the new default)?

Another possibility is that I create manually the backports, removing the new behaviour in the process.

@pitrou
Copy link
Member

@pablogsal As is the most convenient for you.

pablogsaland others added2 commitsMarch 9, 2020 10:17
Co-Authored-By: Victor Stinner <vstinner@python.org>
Co-Authored-By: Victor Stinner <vstinner@python.org>
@pablogsal
Copy link
MemberAuthor

LGTM. Thanks for all updates I asked for ;-)

Always happy to do them! Thanks for the review :)

@pablogsalpablogsal merged commit6012f30 intopython:masterMar 9, 2020
@pablogsalpablogsal deleted the bpo-39850 branchMarch 9, 2020 13:48
pablogsal added a commit to pablogsal/cpython that referenced this pull requestMar 9, 2020
…ythonGH-18866)(cherry picked from commit6012f30)Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
pablogsal added a commit to pablogsal/cpython that referenced this pull requestMar 9, 2020
…ssing (pythonGH-18866)(cherry picked from commit6012f30)Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>.(cherry picked from commit5e217bb)Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
@AmirHmZz
Copy link

So now does windows supportAF_UNIX for IPC ?

Yhg1s pushed a commit that referenced this pull requestOct 20, 2022
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+ via#18866 while fixing#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.
miss-islington pushed a commit to miss-islington/cpython that referenced this pull requestOct 20, 2022
…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-islington pushed a commit to miss-islington/cpython that referenced this pull requestOct 20, 2022
…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-islington pushed a commit to miss-islington/cpython that referenced this pull requestOct 20, 2022
…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-islington pushed a commit to miss-islington/cpython that referenced this pull requestOct 20, 2022
…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-islington added a commit that referenced this pull requestOct 20, 2022
…GH-98501) (GH-98503)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+ via#18866 while fixing#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>Automerge-Triggered-By: GH:gpshead
miss-islington added a commit that referenced this pull requestOct 20, 2022
…GH-98501) (GH-98502)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+ via#18866 while fixing#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>Automerge-Triggered-By: GH:gpshead
pablogsal pushed a commit that referenced this pull requestOct 22, 2022
…GH-98501) (GH-98502)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+ via#18866 while fixing#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>Automerge-Triggered-By: GH:gpshead
ambv pushed a commit that referenced this pull requestOct 28, 2022
…H-98501) (#98504)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+ via#18866 while fixing#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>
frenzymadness pushed a commit to fedora-python/cpython that referenced this pull requestNov 9, 2022
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>Automerge-Triggered-By: GH:gpshead
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@vstinnervstinnervstinner approved these changes

@pitroupitroupitrou left review comments

Assignees

@pablogsalpablogsal

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@pablogsal@pitrou@AmirHmZz@vstinner@the-knights-who-say-ni@bedevere-bot
[8]ページ先頭
©2009-2025 Movatter.jp