IIUC, it takes something like 32k of /dev/random to initialize apr_random.

APR_RANDOM_DEFAULT_POOLS*APR_RANDOM_DEFAULT_RESEED_SIZE*APR_RANDOM_DEFAULT_G_FOR_INSECURE
(32*32*32)

But ap_init_rng() does this with ~4000 8-byte reads of /dev/random.

I am working on a platform where access to the crypto facility
underneath /dev/random is sometimes audited.  Does anyone have any
hints about whether larger reads from /dev/random would be better
elsewhere? Or if the startup requirement is really this high for data
from /dev/random?

Reply via email to