[New-bugs-announce] [issue22542] Use syscall (eg. arc4random or getentropy) rather than /dev/urandom when possible
report at bugs.python.org
Thu Oct 2 19:47:40 CEST 2014
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.
title: Use syscall (eg. arc4random or getentropy) rather than /dev/urandom when possible
versions: Python 3.3
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce