X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=FAQ;h=86b6617f4479456b6bc9f6938a9079f0b538a8f2;hp=30913a11b3039fb3b8a6dbfa861e2c1a95364e09;hb=8d3509b93728a16f5ba830b04a8fe9e879bdd8df;hpb=788e67e227106454a2fb708b94b030883a8a10c2 diff --git a/FAQ b/FAQ index 30913a11b3..86b6617f44 100644 --- a/FAQ +++ b/FAQ @@ -46,6 +46,8 @@ OpenSSL - Frequently Asked Questions * Why does the OpenSSL test suite fail on MacOS X? * Why does the OpenSSL test suite fail in BN_sqr test [on a 64-bit platform]? * Why does OpenBSD-i386 build fail on des-586.s with "Unimplemented segment type"? +* Why does the OpenSSL test suite fail in sha512t on x86 CPU? +* Why does compiler fail to compile sha512.c? [PROG] Questions about programming with OpenSSL @@ -141,8 +143,8 @@ less Unix-centric, it might have been used much earlier. With version 0.9.6 OpenSSL was extended to interface to external crypto hardware. This was realized in a special release '0.9.6-engine'. With -version 0.9.7 (not yet released) the changes were merged into the main -development line, so that the special release is no longer necessary. +version 0.9.7 the changes were merged into the main development line, +so that the special release is no longer necessary. * How do I check the authenticity of the OpenSSL distribution? @@ -598,6 +600,23 @@ Reportedly elder *BSD a.out platforms also suffer from this problem and remedy should be same. Provided binary is statically linked and should be working across wider range of *BSD branches, not just OpenBSD. +* Why does the OpenSSL test suite fail in sha512t on x86 CPU? + +If the test program in question fails withs SIGILL, Illegal Instruction +exception, then you more than likely to run SSE2-capable CPU, such as +Intel P4, under control of kernel which does not support SSE2 +instruction extentions. See accompanying INSTALL file and +OPENSSL_ia32cap(3) documentation page for further information. + +* Why does compiler fail to compile sha512.c? + +OpenSSL SHA-512 implementation depends on compiler support for 64-bit +integer type. Few elder compilers [ULTRIX cc, SCO compiler to mention a +couple] lack support for this and therefore are incapable of compiling +the module in question. The recommendation is to disable SHA-512 by +adding no-sha512 to ./config [or ./Configure] command line. Another +possible alternative might be to switch to GCC. + [PROG] ======================================================================== * Is OpenSSL thread-safe?