4/23 Security question: assuming i have a "good" /dev/random and I
read from /dev/random from 00:00 to 00:01 and save that in a file,
will take make it trivial to attack someome who uses /dev/random on
the same machine to "seed" a random passwd generator at 00:00:30?
Or does each caller some how whiten it with his own environment?
\_ Or say I read in 10k bytes from /dev/random or /dev/urandom
at 00:00 and I start and another copy of the same process "at
the same time", will I get overlapping random streams?
at 00:00, which takes 2 seconds. I start and another copy of
the same process a couple of millisenconds after 00:00,
will I get overlapping or interleaved random streams?
\_ no and no, if it is a "good" /dev/random
\_ So what prevents two people "simultaneously" reading from
/dev/random from letting the same stream?
\_ The driver probably has a locking mechanism in the
read entry point to prevent this:
ep_read { lock ; copy bit to userspace ; unlock ; } |