The
rndtest
driver
"hooks up"
to hardware crypto devices to monitor the
entropy data passed to the
random(4)
subsystem.
This data is periodically tested for FIPS 140-2 compliance and
statistics are collected.
If the harvested entropy fails any of the FIPS test suite, then
it is discarded and testing is continuously applied until
"good data"
is received from the device.
Failures are optionally reported on the console.