From d9248e57807fa6f2a4b8d290fc5f60d4ec1c4552 Mon Sep 17 00:00:00 2001 From: Andy Polyakov Date: Sun, 9 Jan 2005 20:42:33 +0000 Subject: [PATCH] FAQ update to mention no-sha0 as possible workaround for Tru64 compiler bug. Well, no-options seem to be busted in HEAD currently, which should/will be fixed one way or another (see PR#989 for a possible alternative). --- FAQ | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/FAQ b/FAQ index fd354b3b40..12f3d24d16 100644 --- a/FAQ +++ b/FAQ @@ -473,6 +473,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"? -- 2.25.1