> An alternative would be for someone else to package the new version as > rng-tools4, or just submit a patch adding RDRAND support to the > unofficial fork. I didn't accept the TPM patches because it would > clash with the kernel and the rest of the userspace TPM stack, but > RDRAND is different.
I backported RDRAND support to the unofficial fork. Could you please review: http://mentors.debian.net/package/rng-tools https://github.com/cernekee/rng-tools/commits/master aka: git clone git://github.com/cernekee/rng-tools I created an "upstream/2-unofficial-mt.15" release on the upstream branch, then merged it to master and added the debian/ changes on top. Tested with: Debian sid Ubuntu Precise and Quantal RDRAND (Ivy Bridge Core i5) No RNG case (VirtualBox) No AES-NI case (fall back to libgcrypt) gcc -m32 rngd -r /dev/urandom lintian -IE --pedantic Not tested with an actual non-RDRAND HW RNG. :( rngtest FIPS pass/fail results were indistinguishable from those of the upstream rng-tools 4. Also, the performance variations between AES-NI and libgcrypt mirrored the rng-tools 4 results. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
