diff options
author | Lutz Jänicke <jaenicke@openssl.org> | 2007-09-24 11:01:18 +0000 |
---|---|---|
committer | Lutz Jänicke <jaenicke@openssl.org> | 2007-09-24 11:01:18 +0000 |
commit | 7bbce69721077ad1f17a0b428b4f8f76bdf829e1 (patch) | |
tree | 9018ba0c360b471e16c7aae88eaff08880928952 /FAQ | |
parent | 870d6541f2d8a6701354e66c7c221f41dc21c0bc (diff) |
Port from 0.9.8-stable
Diffstat (limited to 'FAQ')
-rw-r--r-- | FAQ | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -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? =============================================================================== @@ -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. |