eg, maybe even something as simple as: --- rng-tools~ 2016-06-04 21:07:26.000000000 -0400 +++ rng-tools 2016-06-04 21:08:53.028515054 -0400 @@ -17,3 +17,4 @@ #RNGDOPTIONS="--hrng=intelfwh --fill-watermark=90% --feed-interval=1" #RNGDOPTIONS="--hrng=viakernel --fill-watermark=90% --feed-interval=1" #RNGDOPTIONS="--hrng=viapadlock --fill-watermark=90% --feed-interval=1" +#RNGDOPTIONS="--fill-watermark=90% --feed-interval=1" # <- for tpm_rng use
On 4 June 2016 at 21:06, Nicholas D Steeves <nstee...@gmail.com> wrote: > Also, it would be good to document somewhere that, --hrng=driver needs > to be omitted eg: > RNGDOPTIONS="--fill-watermark=90% --feed-interval=1" > > cat /proc/sys/kernel/random/entropy_avail hovers close to 4000 after > this is enabled on my Thinkpad. Without it, it hovers around between > the mid-to-high-2000s, and it sometimes dips below 2000 without these > options. > > On my Xeon server, it hovers around the mid-3000s with these > RNGDOPTIONS, and hovers around the mid-2000s without; it also > sometimes dips below 2000 without these options. > > I'd be happy to use the ent suite to compare without tpm_rng, with > tpm_rng and rng-tools, and with tpm_rng, rng-tools, and these > RNGDOPTIONS, if that data is necessary to justify this near-trivial > documentation update. > > Cheers, > Nicholas
