| 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: <ek546d$icj$1@sea.gmane.org> Date: Thu, 23 Nov 2006 22:34:43 +0100 From: Gunter Ohrner <G.Ohrner@...t.rwth-aachen.de> To: linux-kernel@...r.kernel.org Subject: Re: Entropy Pool Contents Lennart Sorensen wrote: > Only some devices/drivers generate entropy data. Some network drivers, Yes, I know, but block device operations should, and directly feeding data into /dev/*random, as I did, definitely should. This machine usually has only very limited entropy available, but the pool currently seeems to bee stuck at "0" - there's no way to get it to even display a slightly different number. That's what confused me pretty much... Normally doing disk IO helps a bit, but it currently does not at all. > pcnet32 and the 8250 driver to generate entropy since otherwise I tended > to run out very quickly. I guess I also should do that - as this machine has several network cards on different networks, that will be definiteely more seecure than running with a completely empty entropy pool stuck at zero bits for several days in a row... 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