Package: rng-tools
Version: 2-unofficial-mt.14-1
Tags: patch
With a fresh install on a Xeon 1226 v3, reading 52KiB from /dev/random
occurs at ~20bits/s
Adding haveged gets it up to the ~60bits/s range
But wow, adding the TPM's TRNG gets it as high as ~2.58MiB/s !
Removing haveged at this point drops it to ~1.68KiB/s
Adding haveged bumps it back up again...
Yeah, something seems strange with these haveged results, but the
improvement from ~20bits/s to ~1.68KiB/s by mixing tpm_rng into the
pool is a *massive* improvement. I used pv -pabet /dev/random >
/dev/null for my casual tests, and manually interrupted once the 52KiB
target was read.
Please use something like the following to patch the README:
diff -ur rng-tools-2-unofficial-mt.14.orig/README
rng-tools-2-unofficial-mt.14/README
--- rng-tools-2-unofficial-mt.14.orig/README 2011-06-17
23:06:56.000000000 -0400
+++ rng-tools-2-unofficial-mt.14/README 2016-05-30 20:28:48.201323887 -0400
@@ -74,6 +74,10 @@
A: Sorry, but you DON'T have a working TRNG. Refer to the "testing rngd"
section for more details.
+* Q: "I can't get the Intel TRNG to work, but I have a TPM. Can I use it?"
+ A: Yes, like this: modprobe tpm-rng && echo tpm-rng >> /etc/modules && \
+ echo "Your TPM's TRNG has been enabled"
+
* Q: "I see no errors anywhere, but rngd doesn't appear to be working. Why?"
A: See the "testing rngd" section for details.
