Re: [openssl.org #92] Prototypes SSL_write() & SSL_read() problem in openssl/ssl.h for 64-bit applications

Richard, The platforms are Irix 6.5.15m with the MIPSpro 7.3.1.3m compiler suite & Solaris 8 with the Forte 6 update 2 with all patches applied. Darin Broady [EMAIL PROTECTED] Lexmark International, Inc. __ OpenSSL Project

Re: Prototypes SSL_write() & SSL_read() problem in openssl/ssl.h for 64-bit applications

The same also goes for CRYPTO_malloc(int, char *, int). It probably should be CRYPTO_malloc(size_t, char *, int). The same would go for CRYPTO_realloc() and CRYPTO_remalloc(). Darin Broady [EMAIL PROTECTED] Lexmark International, Inc. "Darin_Broady/Lex/Lexmark.LEXMARK"@sweeper.lex

Prototypes SSL_write() & SSL_read() problem in openssl/ssl.h for 64-bit applications

The prototype for SSL_write() and SSL_read() both have their last parameters to be int. I believe that this last parameter needs to be of type size_t. Two reasons for doing this: 1) This will allow applications to be compiled in either 32-bit or 64-bit mode without any warnings from the

Possible bug in OpenSSL-0.9.6d/crypto/asn1/a_utctm.c

I believe that I have found a bug in the above file and would like for someone else to santiy check it. At line 290 in a_utctm.c, a separate code block is being used if the library needs to call gmtime_r() to get the time structure. The value is stored in a temporary (data) that is declared i