News for hackers. Stuff that matters.
Re:/dev/random – a new approach by thaumasiotes on Sunday April 24, 2016 @07:19PM (#11561803)
> wait, I'm not dignifying /dev/random: it refuses to provide output at random

Why would this be a problem? Read one byte from /dev/random, and observe one of 257 possible values chosen at random. :D

Re:/dev/random – a new approach by eru on Sunday April 24, 2016 @08:10PM (#11561922)
You'd have to correct for the biases. Not only in probability, but subsequent calls are also not independent.
Re:/dev/random – a new approach by thaumasiotes on Sunday April 24, 2016 @09:38PM (#11562148)
Sure, I realize that. (Although "subsequent calls are not independent" means it's not actually refusing to respond "at random".) I'm just pointing out in a facetious, emoticon-marked manner that "it behaves randomly" is kind of an odd insult to level against a source of randomness.
Re:/dev/random – a new approach by lomnakkus on Monday April 25, 2016 @01:47AM (#11562649)
I think the point is that it should behave predictably (but of course give you random data). Behavior is a "larger" concept than just what kind of data you get from a thing.
Re:/dev/random – a new approach by kzrdude on Monday April 25, 2016 @06:21AM (#11563380)
You can quite predictably drain dev/random and make it not respond randomly. in the 257-valued joke's terms, you can force it to always emit the blocking behavior.