>    3.  In the new "crypto/whrlpool" code, "wp_block.c" causes problems
> on the VAX, where there is no 64-bit integer type to use for "u64". 
> There seems to be code in there which pretends that the size of u64 is
> open to discussion ("sizeof(u64)"), but it seems (to me) to be pretty
> clear that other things will break if it's not 64 bits.
> 
>    I assume that this stuff can be disabled on the VAX, but I haven't
> yet looked for a standard method for doing that.  (Assuming that no one
> has any nice 32-bit code to insert to obviate that.)

   Looking through makevms.com, I noticed this:

$ CONFIG_LOGICALS := 
NO_ASM,NO_RSA,NO_DSA,NO_DH,NO_MD2,NO_MD5,NO_RIPEMD,WHRLPOOL,-
        NO_SHA,NO_SHA0,NO_SHA1,NO_DES/NO_MDC2;NO_MDC2,NO_RC2,NO_RC4,NO_RC5,-
        NO_IDEA,NO_BF,NO_CAST,NO_CAMELLIA,NO_SEED,NO_HMAC,NO_SSL2

I suspect that one could adjust this to add VAX/non-VAX conditionality
for WHRLPOOL, although it might help to spell it "WHIRLPOOL", because
the code seems to be looking for "OPENSSL_NO_WHIRLPOOL", not
"OPENSSL_NO_WHRLPOOL".

   Has anyone looked at this list in recent times to see if the items in
it still make sense?

------------------------------------------------------------------------

   Steven M. Schweda               s...@antinode-info
   382 South Warwick Street        (+1) 651-699-9818
   Saint Paul  MN  55105-2547
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to