summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDr. Stephen Henson <steve@openssl.org>2007-09-20 11:32:09 +0000
committerDr. Stephen Henson <steve@openssl.org>2007-09-20 11:32:09 +0000
commit015052cf7b353ee6a7be0318f48d871979dac902 (patch)
treea28832b9b64e9a7a08060e15d378120126ba8127
parent9ce3ee47ba21fd19859cf2953ee7e951f53e7da7 (diff)
Clarify wording a little.
-rw-r--r--FAQ18
1 files changed, 8 insertions, 10 deletions
diff --git a/FAQ b/FAQ
index e00651e9c5..e2e1c2f92e 100644
--- a/FAQ
+++ b/FAQ
@@ -897,16 +897,14 @@ thread-safe):
* Why does Valgrind complain about the use of uninitialized data?
-OpenSSL does internally call its own PRNG routines to retrieve random
-numbers. It so does with uninitialed buffer contents. The buffer
-contents is mixed into the entropy pool so that it technically does
-not matter whether the buffer is initialized at this point or not.
-Valgrind (and other test tools) will complain whatsoever. When
-using Valgrind, make sure to use an OpenSSL library that has been
-compiled with the PEDANTIC macro being defined (-DPEDANTIC) to
-get rid of these warnings. Compling with -DPURIFY will help as well.
-
-The PEDANTIC macro was added in OpenSSL 0.9.8f.
+When OpenSSL's PRNG routines are called to generate random numbers the supplied
+buffer contents are mixed into the entropy pool: so it technically does not
+matter whether the buffer is initialized at this point or not. Valgrind (and
+other test tools) will complain about this. When using Valgrind, make sure the
+OpenSSL library has been compiled with the PEDANTIC macro defined (-DPEDANTIC)
+to get rid of these warnings. Compling with -DPURIFY will help as well.
+
+The use of PEDANTIC with the PRNG was added in OpenSSL 0.9.8f.
===============================================================================