3 ms·
how does that contradict the person you're replying to? surely it would be a non-blocking read that would return empty. you seem to be saying that apps genera
by andrewcooke 14y ago
how does that contradict the person you're replying to? surely it would be a non-blocking read that would return empty.
you seem to be saying that apps generally should need /dev/random only rarely. which seems sensible, but is also what the post one up suggested.
in short you seem to be in confused and annoyed agreement.
[vaguely related interesting post on urandom quality - http://security.stackexchange.com/questions/3936/is-a-rand-from-dev-urandom-secure-for-a-login-key/3939#3939 http://security.stackexchange.com/questions/3936/is-a-rand-f...]
- marshray 14y agoI'm saying that regardless of whether /dev/random is read with a blocking call, it shouldn't ever block. (Except during initial seeding right at startup). +1 on the linked post.