[issue22542] Use syscall (eg. arc4random or getentropy) rather than /dev/urandom when possible

[700eb415]

New submission from 700eb415:

Trying to run the python interpreter in a chroot fails if /dev/urandom is not present. Removing the "nodev" flag from the filesystem is not ideal in many situations.

Instead, we should utilize functions such as OpenBSD's arc4random(3) and the new potential getentropy() Linux syscall. Alternatively, libevent provides a portable version of arc4random(3) as a workaround.

This issue has been discussed extensively when forking LibreSSL. Since we're already providing win32 exceptions, we should at least use the syscall rather than device if it's defined.

----------
components: Build
messages: 228246
nosy: 700eb415
priority: normal
severity: normal
status: open
title: Use syscall (eg. arc4random or getentropy) rather than /dev/urandom when possible
versions: Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22542>
_______________________________________