summaryrefslogtreecommitdiffstats
path: root/FAQ
diff options
context:
space:
mode:
authorLutz Jänicke <jaenicke@openssl.org>2007-09-21 10:10:47 +0000
committerLutz Jänicke <jaenicke@openssl.org>2007-09-21 10:10:47 +0000
commit29f4b05954073aece823784f7309d8778bff2aa7 (patch)
treeb35dbd947867ef6c259aed03155951bb5f143cfe /FAQ
parent48ca0c99b2bf78c756fe96d1ac71b66cd0b1a38a (diff)
The use of the PURIFY macro in ssleay_rand_bytes() is sufficient to
resolve the Valgrind issue with random numbers. Undo the changes to RAND_bytes() and RAND_pseudo_bytes() that are redundant in this respect. Update documentation and FAQ accordingly, as the PURIFY macro is available at least since 0.9.7.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ2
1 files changed, 0 insertions, 2 deletions
diff --git a/FAQ b/FAQ
index 4a1fb5f94e..c56dbadc9d 100644
--- a/FAQ
+++ b/FAQ
@@ -904,8 +904,6 @@ other test tools) will complain about this. When using Valgrind, make sure the
OpenSSL library has been compiled with the PURIFY macro defined (-DPURIFY)
to get rid of these warnings
-The use of PURIFY with the PRNG was added in OpenSSL 0.9.8f.
-
===============================================================================