> > Making /dev/random block if the amount requirements aren't met makes sense > > to me. If I request x bytes of random stuff, and get less, I probably > > reread /dev/random. If it's entropy pool is exhausted it makes sense to be > > to block. > > This is the job of the program accessing /dev/random. Open it blocking or > non-blocking and read until you satisfy your read buffer. Agree, if randomness is guaranteed in that case. I usually bail out in that case. Time to change that :) > -d Igmar - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: /dev/random probs in 2.4test(12-pre3) H. Peter Anvin
- Re: /dev/random probs in 2.4test(12-pre3) Albert D. Cahalan
- Re: /dev/random probs in 2.4test(12-pre3) Igmar Palsenberg
- Re: /dev/random probs in 2.4test(12-pre3) Jeff Garzik
- Re: /dev/random probs in 2.4test(12-pre3) Igmar Palsenberg
- Re: /dev/random probs in 2.4test(12-pre3) David Ford
- Re: /dev/random probs in 2.4test(12-pre3) H. Peter Anvin
- Re: /dev/random probs in 2.4test(12-pre3) Kai Henningsen
- Re: /dev/random probs in 2.4test(12-pre3) Igmar Palsenberg
- Re: /dev/random probs in 2.4test(12-pre3) David Ford
- Re: /dev/random probs in 2.4test(12-pre3) Igmar Palsenberg
- Re: /dev/random probs in 2.4test(12-pre3) H. Peter Anvin
- Re: /dev/random probs in 2.4test(12-pre3) H. Peter Anvin