Cc: Alan Cox <alan@...>, Jeff Garzik <jeff@...>, <netdev@...>, <linux-kernel@...>, Andrew Morton <akpm@...>, Brandeburg, Jesse <jesse.brandeburg@...>, Chris Peterson <cpeterso@...>, <tpmdd-devel@...>, <tpm@...>, Herbert Xu <herbert@...>
No in this case /dev/urandom is the wrong choice. You should seed
then some standard RND with the time,pid as is the classical way
and not use any precious entropy. Yes some programs don't do that,
but they're wrong and actually slightly dangerous.
Even the cryptographic programs normally use /dev/urandom to get
session keys etc. That is because they are definitely concerned about
local DoS. Just strace your ssh daemon or your SSL web server to see
what I mean.
Yes, but if you read the context of that patch it commented out
the code that accessed /dev/urandom!
Please reread my analysis of the issue. If you have already entropy in
the pool the additional feed doesn't change anything. And if you don't
it still stays the same.
-Andi
--
