Messages in this thread | | | Date | Wed, 23 Jul 2014 16:52:21 +0300 | Subject | Reading large amounts from /dev/urandom broken | From | Andrey Utkin <> |
| |
Dear developers, please check bugzilla ticket https://bugzilla.kernel.org/show_bug.cgi?id=80981 (not the initial issue, but starting with comment#3.
Reading from /dev/urandom gives EOF after 33554431 bytes. I believe it is introduced by commit 79a8468747c5f95ed3d5ce8376a3e82e0c5857fc, with the chunk
nbytes = min_t(size_t, nbytes, INT_MAX >> (ENTROPY_SHIFT + 3));
which is described in commit message as "additional paranoia check to prevent overly large count values to be passed into urandom_read()".
I don't know why people pull such large amounts of data from urandom, but given today there are two bugreports regarding problems doing that, i consider that this is practiced.
-- Andrey Utkin
| |