Avoid aliasing warning.

[openssl.git] / FAQ

diff --git a/FAQ b/FAQ
index 13f7c3ddec6e7d6d2e861388dc9f7b69da537744..d337d90ff09a3194d6ed8b7a3c38b0df3b22e59f 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -67,6 +67,7 @@ OpenSSL  -  Frequently Asked Questions
 * Why doesn't my server application receive a client certificate?
 * Why does compilation fail due to an undefined symbol NID_uniqueIdentifier?
 * I think I've detected a memory leak, is this a bug?
+* Why does Valgrind complain about the use of uninitialized data?
 * Why doesn't a memory BIO work when a file does?
 
 ===============================================================================
@@ -76,7 +77,7 @@ OpenSSL  -  Frequently Asked Questions
 * Which is the current version of OpenSSL?
 
 The current version is available from <URL: http://www.openssl.org>.
-OpenSSL 0.9.8c was released on September 5th, 2006.
+OpenSSL 0.9.8g was released on October 19th, 2007.
 
 In addition to the current stable release, you can also access daily
 snapshots of the OpenSSL development version at <URL:
@@ -917,6 +918,16 @@ thread-safe):
   ERR_free_strings(), EVP_cleanup() and CRYPTO_cleanup_all_ex_data().
 
 
+* Why does Valgrind complain about the use of uninitialized data?
+
+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 PURIFY macro defined (-DPURIFY)
+to get rid of these warnings.
+
+
 * Why doesn't a memory BIO work when a file does?
 
 This can occur in several cases for example reading an S/MIME email message.
@@ -935,6 +946,8 @@ is needed. This must be done by calling:
 
    BIO_set_mem_eof_return(bio, 0);
 
+See the manual pages for more details.
+
 
 ===============================================================================