It's interesting to see this happening. We have two parts of OpenSSL, sha512 and pqueue, that solve the 64-bit integer problem in very different manners.
Would it be a bad thing to have a header file in crypto/bn that provides a guaranteed 64-bit number, possibly through BIGNUM, with macros to distinguish between the true 64-bit integer and BIGNUM cases (like pq_compat.h has today), and have both sha512 and pqueue use it? I'm not saying that sha512 should be implemented using BINUMs, but rather that it should be possible to detect if 64-bit integers are support as far as OpenSSL knows, and have sha512 implemented in those terms instead of forcing the user to say no-sha512 because his first build failed? In message <[EMAIL PROTECTED]> on Mon, 6 Jun 2005 11:32:03 +0200 (CEST), "Andy Polyakov" <[EMAIL PROTECTED]> said: appro> OpenSSL CVS Repository appro> http://cvs.openssl.org/ appro> ____________________________________________________________________________ appro> appro> Server: cvs.openssl.org Name: Andy Polyakov appro> Root: /v/openssl/cvs Email: [EMAIL PROTECTED] appro> Module: openssl Date: 06-Jun-2005 11:32:02 appro> Branch: HEAD Handle: 2005060610320100 appro> appro> Modified files: appro> openssl FAQ appro> appro> Log: appro> FAQ to mention no-sha512 as option for compilers without support for 64-bit appro> integer type. appro> appro> Summary: appro> Revision Changes Path appro> 1.103 +10 -0 openssl/FAQ appro> ____________________________________________________________________________ appro> appro> patch -p0 <<'@@ .' appro> Index: openssl/FAQ appro> ============================================================================ appro> $ cvs diff -u -r1.102 -r1.103 FAQ appro> --- openssl/FAQ 19 May 2005 19:54:49 -0000 1.102 appro> +++ openssl/FAQ 6 Jun 2005 09:32:01 -0000 1.103 appro> @@ -47,6 +47,7 @@ appro> * Why does the OpenSSL test suite fail in BN_sqr test [on a 64-bit platform]? appro> * Why does OpenBSD-i386 build fail on des-586.s with "Unimplemented segment type"? appro> * Why does the OpenSSL test suite fail in sha512t on x86 CPU? appro> +* Why does compiler fail to compile sha512.c? appro> appro> [PROG] Questions about programming with OpenSSL appro> appro> @@ -607,6 +608,15 @@ appro> instruction extentions. See accompanying INSTALL file and appro> OPENSSL_ia32cap(3) documentation page for further information. appro> appro> +* Why does compiler fail to compile sha512.c? appro> + appro> +OpenSSL SHA-512 implementation depends on compiler support for 64-bit appro> +integer type. Few elder compilers [ULTRIX cc, SCO compiler to mention a appro> +couple] lack support for this and therefore are incapable of compiling appro> +the module in question. The recommendation is to disable SHA-512 by appro> +adding no-sha512 to ./config [or ./Configure] command line. Another appro> +possible alternative might be to switch to GCC. appro> + appro> [PROG] ======================================================================== appro> appro> * Is OpenSSL thread-safe? appro> @@ . appro> ______________________________________________________________________ appro> OpenSSL Project http://www.openssl.org appro> CVS Repository Commit List [EMAIL PROTECTED] appro> Automated List Manager [EMAIL PROTECTED] appro> ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
