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 vstinner
Recipients 700eb415, alex, ncoghlan, rpointel, vstinner
Date 2016-09-20.21:50:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474408249.48.0.311923232912.issue22542@psf.upfronthosting.co.za>
In-reply-to
Content
"Trying to run the python interpreter in a chroot fails if /dev/urandom is not present."

The workaround is simple: fix your chroot to correctly expose /dev/urandom in the chroot. It's a common and known issue, no?

Since the issue is almost dead since 2 years and I don't know if arc4random() is suitable for os.urandom(), I close the issue. If you want to reopen it, please come back with more information on arc4random() security ;-)
History
Date User Action Args
2016-09-20 21:50:49vstinnersetrecipients: + vstinner, ncoghlan, alex, rpointel, 700eb415
2016-09-20 21:50:49vstinnersetmessageid: <1474408249.48.0.311923232912.issue22542@psf.upfronthosting.co.za>
2016-09-20 21:50:49vstinnerlinkissue22542 messages
2016-09-20 21:50:49vstinnercreate