FAQ update to mention no-sha0 as possible workaround for Tru64 compiler bug.

diff --git a/FAQ b/FAQ
index 1c232c3c54b88c8f2ed133363c9326f45d422966..b695c4490cddc42d134c7b0a2985382e65902c2c 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -472,6 +472,10 @@ This will only compile sha_dgst.c with -O0, the rest with the optimization
 level chosen by the configuration process.  When the above is done, do the
 test and installation and you're set.
 
+3. Reconfigure the toolkit with no-sha0 option to leave out SHA0. It
+should not be used and is not used in SSL/TLS nor any other recognized
+protocol in either case.
+
 
 * Why does the OpenSSL compilation fail with "ar: command not found"?