At 12:59 9/23/2013 -0700, Michael Sierchio wrote:
>
>I'll repeat myself - the fact that the
>/dev/random implementation you're using
>blocks is a serious design flaw.
Convince Linus, the GPG developers et al.--not me.
Till then I respect their view as embodied
by the latest implementation of rand
At 20:27 9/23/2013 +0200, Richard Könning wrote:
>/dev/random is a PRNG which blocks when the (crude)
>entropy estimation of the entropy pool falls below a
>limit. Besides this there are afaik no big
>differences between /dev/random and /dev/urandom.
In the sense that all TRNG outputs are run
th
No /dev/urandom is a PRNG. /dev/random
is a TRNG. Read the code
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/random.c?id=272b98c6455f00884f0350f775c5342358ebb73f
The TPM here generates 40Kbits/sec, or
5000 bytes/sec--more than enough for the
situation at han
Not interested in BSD or Yarrow PRNG.
Not interested in any PRNG.
Interested in True RNG from hardware
as mixed by Theodore Ts'o excellent,
predominant and continually evolving
(https://lkml.org/lkml/2013/9/13/624)
"/dev/random". Have more than enough
TRNG for the needs of the servers in
question
Hello,
I'm interested in having 'openssl' version 1.0.1e
make use, by default, of hardware generated
true random numbers for creating session keys.
So far I've configured a STElectronics ST33
TPM as the majority source of /dev/random
entropy by configuring and starting the
'rngd' daemon from 'rng
