How experimental is --enable-random-daemon?
ametzler at downhill.at.eu.org
Mon Mar 10 19:24:52 CET 2008
since using a random seed file for exim does not work reliably with
the (perhaps broken) patch
I am considering the other easy way, using --enable-random-daemon.
However I am unsure on whether --enable-random-daemon will eat small
children or whether it simply is not built by default but should work
alright. Would you outright recommed against using it in production
Other stuff I have been wondering about:
- A pid file would be nice.
- Why isn't the daemon used by default if specified at compile time?
Needing to patch every gcrypt using application (or at least
libgnutls) to get best benefits seems to be suboptimal.
gcry_control (GCRYCTL_USE_RANDOM_DAEMON, 1)
thanks, cu andreas
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
More information about the Gcrypt-devel