diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2022-10-28 10:08:30 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-28 10:08:30 (GMT) |
| commit | b43496c01a554cf41ae654a0379efae18609ad39 (patch) | |
| tree | 5c53fae3c8f1c3d953215427a9762d58b21f3f78 /Python/pyctype.c | |
| parent | 857efee6d2d43c5c12fc7e377ce437144c728ab8 (diff) | |
| download | cpython-b43496c01a554cf41ae654a0379efae18609ad39.zip cpython-b43496c01a554cf41ae654a0379efae18609ad39.tar.gz cpython-b43496c01a554cf41ae654a0379efae18609ad39.tar.bz2 | |
[3.9] gh-97514: Don't use Linux abstract sockets for multiprocessing (GH-98501) (#98504)
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
https://github.com/python/cpython/pull/18866 while fixing
https://github.com/python/cpython/issues/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 49f61068f49747164988ffc5a442d2a63874fc17)
Co-authored-by: Gregory P. Smith <greg@krypto.org>
Diffstat (limited to 'Python/pyctype.c')
0 files changed, 0 insertions, 0 deletions