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 jbeck
Recipients dstufft, jbeck, tim.peters, vstinner
Date 2015-09-11.17:11:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, those patches work, with a caveat.  While testing this, I found out why I had needed EINVAL earlier (and still do, for now): there is a bug in the Solaris implementation of getrandom(2).  If flags are 0 and the buffer size > 1024, then it fails with EINVAL.  That is only supposed to happen for a buffer that big if GNRD_RANDOM is set in flags but GNRD_NONBLOCK is not set.  So until that bug is fixed, I have to patch py_getrandom() to treat EINVAL like ENOSYS and fall back to using /dev/urandom as if getrandom(2) were not supported.
Date User Action Args
2015-09-11 17:11:41jbecksetrecipients: + jbeck, tim.peters, vstinner, dstufft
2015-09-11 17:11:41jbecksetmessageid: <>
2015-09-11 17:11:41jbecklinkissue25003 messages
2015-09-11 17:11:41jbeckcreate