In message <[email protected]> on Wed, 31 Mar 2010 09:15:51
-0500 (CDT), "Steven M. Schweda" <[email protected]> said:
sms> > 3. In the new "crypto/whrlpool" code, "wp_block.c" causes problems
sms> > on the VAX, where there is no 64-bit integer type to use for "u64".
sms> > There seems to be code in there which pretends that the size of u64 is
sms> > open to discussion ("sizeof(u64)"), but it seems (to me) to be pretty
sms> > clear that other things will break if it's not 64 bits.
sms> >
sms> > I assume that this stuff can be disabled on the VAX, but I haven't
sms> > yet looked for a standard method for doing that. (Assuming that no one
sms> > has any nice 32-bit code to insert to obviate that.)
sms>
sms> Looking through makevms.com, I noticed this:
sms>
sms> $ CONFIG_LOGICALS :=
NO_ASM,NO_RSA,NO_DSA,NO_DH,NO_MD2,NO_MD5,NO_RIPEMD,WHRLPOOL,-
sms>
NO_SHA,NO_SHA0,NO_SHA1,NO_DES/NO_MDC2;NO_MDC2,NO_RC2,NO_RC4,NO_RC5,-
sms> NO_IDEA,NO_BF,NO_CAST,NO_CAMELLIA,NO_SEED,NO_HMAC,NO_SSL2
sms>
sms> I suspect that one could adjust this to add VAX/non-VAX conditionality
sms> for WHRLPOOL, although it might help to spell it "WHIRLPOOL", because
sms> the code seems to be looking for "OPENSSL_NO_WHIRLPOOL", not
sms> "OPENSSL_NO_WHRLPOOL".
sms>
sms> Has anyone looked at this list in recent times to see if the items in
sms> it still make sense?
I'm looking at it right now, and I'm reworking the whole thing to make
it more comprehensible for starters ;-)
--
Richard Levitte [email protected]
http://richard.levitte.org/
"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
