From: Lutz Jänicke Date: Mon, 10 Nov 2008 11:26:44 +0000 (+0000) Subject: Clarify (non-)blocking behavior of EGD socket interface used by RAND_egd(). X-Git-Tag: OpenSSL_0_9_8k^2~174 X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=706c5a4d353eeac4b3217138eeea6b737ff14681;p=oweals%2Fopenssl.git Clarify (non-)blocking behavior of EGD socket interface used by RAND_egd(). --- diff --git a/doc/crypto/RAND_egd.pod b/doc/crypto/RAND_egd.pod index 079838ea2e..8b8c61d161 100644 --- a/doc/crypto/RAND_egd.pod +++ b/doc/crypto/RAND_egd.pod @@ -45,8 +45,11 @@ EGD is available from http://www.lothar.com/tech/crypto/ (C to install). It is run as B I, where I is an absolute path designating a socket. When RAND_egd() is called with that path as an argument, it tries to read -random bytes that EGD has collected. The read is performed in -non-blocking mode. +random bytes that EGD has collected. RAND_egd() retrieves entropy from the +daemon using the daemon's "non-blocking read" command which shall +be answered immediately by the daemon without waiting for additional +entropy to be collected. The write and read socket operations in the +communication are blocking. Alternatively, the EGD-interface compatible daemon PRNGD can be used. It is available from