From 1532493dab8c51453eeb38de31f12eef42c485f2 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Lutz=20J=C3=A4nicke?= Date: Mon, 10 Nov 2008 11:26:46 +0000 Subject: [PATCH] Clarify (non-)blocking behavior of EGD socket interface used by RAND_egd(). --- doc/crypto/RAND_egd.pod | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) 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 -- 2.25.1