* Which is the current version of OpenSSL?
The current version is available from <URL: http://www.openssl.org>.
-OpenSSL 0.9.8e was released on February 23rd, 2007.
+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:
* Why do I get errors about unknown algorithms?
-This can happen under several circumstances such as reading in an
-encrypted private key or attempting to decrypt a PKCS#12 file. The cause
-is forgetting to load OpenSSL's table of algorithms with
-OpenSSL_add_all_algorithms(). See the manual page for more information.
-
+The cause is forgetting to load OpenSSL's table of algorithms with
+OpenSSL_add_all_algorithms(). See the manual page for more information. This
+can cause several problems such as being unable to read in an encrypted
+PEM file, unable to decrypt a PKCS#12 file or signature failure when
+verifying certificates.
* Why can't the OpenSSH configure script detect OpenSSL?
* 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 PURIFY macro defined (-DPURIFY)
+to get rid of these warnings.
===============================================================================