[issue27249] Add os.urandom_info

STINNER Victor added the comment: The current trend in the random discussion (see https://haypo-notes.readthedocs.io/pep_random.html and the issue #26839) is more to use weak entropy to start Python (hash seed and random constructor) and os.urandom() blocks until the kernel collected enough

[issue27249] Add os.urandom_info

Christian Heimes added the comment: +1 How are you planning to handle initialization? Run getentropy() and check if the syscall succeeds? -- nosy: +christian.heimes ___ Python tracker

[issue27249] Add os.urandom_info

Changes by Alex Gaynor : -- nosy: +alex ___ Python tracker ___ ___ Python-bugs-list

[issue27249] Add os.urandom_info

New submission from STINNER Victor: It seems like in some cases, you do need to know how os.urandom() generates random numbers. On Linux, using getrandom() to read /dev/urandom in blocking mode or reading from /dev/urandom give a different level of security if the urandom entropy pool is not