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 martin.panter, ncoghlan, petr.viktorin, vstinner
Date 2016-09-20.21:14:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474406057.61.0.996442327891.issue27990@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not excited by the idea of using hardcoded constants for getrandom(). There is a risk of using wrong constants depending on the architecture or the Linux kernel version.

The code is already very low-level: it calls directly the syscall using syscall() function. getrandom() has no nice glibc clean API yet:
https://sourceware.org/bugzilla/show_bug.cgi?id=17252

I suggest to close the issue as WONTFIX. It's ok to use a file descriptor and read /dev/urandom. getrandom() is nice to have, but it's not really a killer feature.

For Fedora: sure, you can use vendor patches to workaround your technical issue, builders using an old kernel :-) But it would be simpler to upgrade the builder, no? :-)
History
Date User Action Args
2016-09-20 21:14:17vstinnersetrecipients: + vstinner, ncoghlan, petr.viktorin, martin.panter
2016-09-20 21:14:17vstinnersetmessageid: <1474406057.61.0.996442327891.issue27990@psf.upfronthosting.co.za>
2016-09-20 21:14:17vstinnerlinkissue27990 messages
2016-09-20 21:14:17vstinnercreate