[issue27955] getrandom() syscall returning EPERM make the system unusable.

2017-03-31 Thread Donald Stufft
Changes by Donald Stufft : -- pull_requests: +826 ___ Python tracker ___ ___

[issue27955] getrandom() syscall returning EPERM make the system unusable.

2016-09-20 Thread STINNER Victor
STINNER Victor added the comment: I modified Python 3.5, 3.6 and 3.7 to fall back on reading /dev/urandom when getrandom() syscall fails with EPERM. Thanks for the bug report iwings! Note: Python 2.7 does not use getrandom() and so is not impacted. Christian: > Did you open a bug with your

[issue27955] getrandom() syscall returning EPERM make the system unusable.

2016-09-20 Thread Roundup Robot
Roundup Robot added the comment: New changeset 41e9e711b9b5 by Victor Stinner in branch '3.5': Cleanup random.c https://hg.python.org/cpython/rev/41e9e711b9b5 New changeset ddc54f08bdfa by Victor Stinner in branch '3.5': Catch EPERM error in py_getrandom()

[issue27955] getrandom() syscall returning EPERM make the system unusable.

2016-09-06 Thread Nick Coghlan
Nick Coghlan added the comment: With #27778 implemented, there's also the question of how os.getrandom() will react to security policies that restrict access to the getrandom syscalls (vs just not having it available in the kernel). -- nosy: +ncoghlan

[issue27955] getrandom() syscall returning EPERM make the system unusable.

2016-09-05 Thread STINNER Victor
STINNER Victor added the comment: I'm ok to fallback on read /dev/urandom device when getrandom() is blocked by a stupid security policy :-) -- ___ Python tracker

[issue27955] getrandom() syscall returning EPERM make the system unusable.

2016-09-05 Thread iwings
iwings added the comment: I did not report this to QNAP yet. but there's already a thread on their forum. https://forum.qnap.com/viewtopic.php?t=124650 (registration required) - ENOSYS is not listed in that man page, but it occurs. - EPERM is not listed in that man page, but it can be returned

[issue27955] getrandom() syscall returning EPERM make the system unusable.

2016-09-05 Thread Christian Heimes
Christian Heimes added the comment: Did you open a bug with your vendor, too? QNAP is clearly violating Kernel APIs. getrandom() is not suppose to fail with EPERM. Valid errnos are EINVAL, EFAULT, EAGAIN and EINTR. http://man7.org/linux/man-pages/man2/getrandom.2.html -- nosy:

[issue27955] getrandom() syscall returning EPERM make the system unusable.

2016-09-05 Thread iwings
New submission from iwings: On QNAP's Linux Station (lxc based virtual environment), getrandom() syscall returns EPERM not ENOSYS when it's not available. (HOST) uname -a Linux **-NAS 3.12.6 #1 SMP Thu Sep 1 00:57:44 CST 2016 x86_64 unknown (HOST) /lib64/libc-2.19.so GNU C Library (Ubuntu