➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Robert Boehne
Recipients Robert Boehne, christian.heimes, jmadden, vstinner
Date 2019-05-10.16:06:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAADOFPGrKbz-fGkaZ1oo2zQ9iD_=Tx5rZAKvB13eyt0-WEgwFQ@mail.gmail.com>
In-reply-to <1557444084.91.0.776066823617.issue36843@roundup.psfhosted.org>
Content 
It doesn't look good:

robb@nepal:/raid/checkouts-raid/robb/nepal$ xlc_r -q64 -O0 -g
-qlanglvl=extc1x -o urandom urandom.c

robb@nepal:/raid/checkouts-raid/robb/nepal$ ./urandom

open O_RDONLY failed

open O_RDONLY | O_CLOEXEC failed

robb@nepal:/raid/checkouts-raid/robb/nepal$ uname -a

AIX nepal 1 7 00FA7FB84C00

robb@nepal:/raid/checkouts-raid/robb/nepal$

On Thu, May 9, 2019 at 6:21 PM STINNER Victor <report@bugs.python.org>
wrote:

>
> STINNER Victor <vstinner@redhat.com> added the comment:
>
> Robert Boehne: pyurandom() uses _Py_open_noraise("/dev/urandom", O_RDONLY)
> which uses O_CLOEXEC if available. If this flag available? Does it work?
>
> Please try to build attached urandom.c.
>
> Example on my Fedora 29:
>
> open O_RDONLY succeeded
> read(16) -> 16
> open O_RDONLY | O_CLOEXEC succeeded
> read(16) -> 16
>
> ----------
> Added file: https://bugs.python.org/file48322/urandom.c
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue36843>
> _______________________________________
>
History
Date User Action Args
2019-05-10 16:06:40Robert Boehnesetrecipients: + Robert Boehne, vstinner, christian.heimes, jmadden
2019-05-10 16:06:40Robert Boehnelinkissue36843 messages
2019-05-10 16:06:40Robert Boehnecreate