From: Andy Polyakov <appro@openssl.org>
Date: Sun, 9 Jan 2005 20:43:49 +0000 (+0000)
Subject: FAQ update to mention no-sha0 as possible workaround for Tru64 compiler bug.
X-Git-Tag: OpenSSL_0_9_7f~51
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=954f3c31264134a8c8cdd81f34e00b2a856527f5;p=oweals%2Fopenssl.git

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

diff --git a/FAQ b/FAQ
index 1c232c3c54..b695c4490c 100644
--- 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"?