-
-
Notifications
You must be signed in to change notification settings - Fork 34.5k
gh-137335: Fix unlikely name conflicts for named pipes in multiprocessing and asyncio on Windows #137389
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
Merged
serhiy-storchaka
merged 9 commits into
python:main
from
serhiy-storchaka:temp-named-pipes
Feb 24, 2026
+57
−26
Merged
gh-137335: Fix unlikely name conflicts for named pipes in multiprocessing and asyncio on Windows #137389
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2a0a5e9
gh-137335: Fix unlikely nmae conflicts for named pipes in multiproces…
serhiy-storchaka 5b91a56
Fix typo
serhiy-storchaka ed050a0
Do not use os.getpid() and tempfile._get_candidate_names().
serhiy-storchaka 7363c99
Merge branch 'main' into temp-named-pipes
serhiy-storchaka 5243b9e
Use os.urandom().
serhiy-storchaka 81cb66e
Merge branch 'main' into temp-named-pipes
serhiy-storchaka 5207bf6
Restore the PID and sequential number for debugging and reducing chan…
serhiy-storchaka cae80b9
Limit the number of attempts.
serhiy-storchaka de04089
Apply suggestion from @serhiy-storchaka
serhiy-storchaka File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Do not use os.getpid() and tempfile._get_candidate_names().
- Loading branch information
commit ed050a03a3870f7477fd5e3ff7eeba61a05b4d92
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
A comment:
we could use
os.urandom(8).hex()but this would only reduce the number of loop iterations we would do until we find a suitable name. OTOH, this makes normal cases much slower (usually, we are not in the presence of an adversary that is trying to create pipes...), so we would be only doing the loop once.Now, I'm actually worried that it if we're able to interact with the process that is creating the pipes, then we could actually recover enough samples from the underlying PRNG instance and get the original seed. But this is only if 1) there are no random calls in between and 2) we can get 624 consecutive 32-bit samples from the random source.
Condition 2) already holds because random.randbytes(8) is actually equivalent to two calls of
random.randbytes(4)that are concatenated. Since reverting MT-19937 requires only consecutive 624 32-bit words, this is the same as doing 312 pipe creations where we don't have calls torandom.*in between (and then inspect the named file). This could be possible in practice, especially if we're talking about the multiprocessing and the asyncio components which could have some interactivness (e.g., a server).Therefore, I would still suggest using
os.urandom(8).hex()even if it slows down the calls.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.
Good catch, I did not thought about this.
Sorry for not answering immediately, I missed your comment.