[EMAIL PROTECTED] wrote:
> and cat'd /dev/random and urandom to /dev/null trying to generate entropy. I don't think you want to mess with getting anything from /dev/random, because you are decreasing the entropy pool when you use it. As an example, you can use dd to read bytes from /dev/random, which does blocking I/O. /dev/random returns bytes from the entropy pool, but only if there are bytes available. If there aren't, it will wait until they are. So dd if=/dev/random of=/tmp/doh bs=1 count=10 will not finish right away and will pause because it doesn't have enough entropy after booting. Sometimes it will, sometimes not. You may get 2 bytes or 8 before it stops to wait. You can change the count to read in fewer bytes and mess around with it to see how it works. So how do you generate entropy? Well the others mentioned some ideas, and I think I use them, just not the freaky python trick :) I've found an easy way to do this when your other program is stuck generating keys, is to switch to anonther terminal like Alt-F2 and login in there and run some stuff like ps, date, and who. Generates plenty of disorder. Cheers, Matthew _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
