Robert Boehne <rboe...@gmail.com> added the comment:
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 <rep...@bugs.python.org>
wrote:
>
> STINNER Victor <vstin...@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 <rep...@bugs.python.org>
> <https://bugs.python.org/issue36843>
> _______________________________________
>
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue36843>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
