Our kernel already does this and more -- and has for a decade, before
everyone else did so.

Doing this in userland makes no sense.

This is the wrong guidance to the entire development community.

Satisfying these test suites is a disaster.  They are testing wrong.

> I would like to import the jitterentropy library.  It generates
> entropy by timing CPU operations and memory access.  Advantage is
> that it also works in virtual environments.
> 
> There exists a daemon that uses this library to seed the kernel.
> But that is another port.
> 
> A NIST testsuite exists to evaluate the entropy of the collected
> data.  There are a bunch of ports missing to run the testsuite.
> The library itself is working fine.
> 
> ok to import jitterentropy-library 3.6.3 ?
> 
> bluhm
> 
> Comment:
> hardware RNG based on CPU timing jitter
> 
> Description:
> The jitterentropy library provides a source of good entropy by collecting
> CPU executing time jitter. The entropy in the CPU execution time jitter
> is magnified by the CPU Jitter Random Number Generator.  The CPU Jitter
> Random Number Generator uses the CPU execution timing jitter to generate
> a bit stream which complies with different statistical measurements that
> determine the bit stream is random.