| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <ek54hf$icj$2@sea.gmane.org> Date: Thu, 23 Nov 2006 22:40:36 +0100 From: Gunter Ohrner <G.Ohrner@...t.rwth-aachen.de> To: linux-kernel@...r.kernel.org Subject: Re: Entropy Pool Contents Jan Engelhardt wrote: >>Hornburg:~# cat /proc/sys/kernel/random/entropy_avail >>0 > You really must have bad luck with your entropy... IMHO something really fishy's going on there. If I explicitely write data into the pool, it shouldd not stay at "zero", from wwhat I understood about how /dev/*random work. > Disk activities are "somewhat predictable", like network traffic, and > hence are not (or should not - have not checked it) contribute to the > pool. Well, they do, block device operations do, using the function add_blkdev_randomness, as far as I know. > Note that urandom is the device which _always_ gives you data, and > when the pool is exhausted, returns pseudorandom data. I know, and running on deterministically computed random values only for days in a row is no situation I'm paticularily happy about... I'm mainly wondering why writing stuff to /dev/*random does not change the entropy from zero to at least any low non-zero value... Greetings, Gunter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists