Need help in Compiling openssl-0.9.8g

Hi, I am new to openssl. I am trying to cross compiling openssl-0.9.8g for linux mipsel. I gave the following command to configure ./Configure shared no-idea no-rc5 --prefix=path to file system linux-mipsel. When I compile by Make command. I am getting the error _dl_out_of_memory

[PATCH] PURIFY and valgrind

Dear, Please find attached a patch which makes valgrind and friends happy. Some changes had been done in md_rand.c which broke the purpose of PURIFY. Needless to say that the define PURIFY is *not* for production system... Best Regards, Frederic Heem

Re: CRYPTO_THREADID_* code in 0.9.9: come gone again? [quick question]

Yep, I'll also be reverting Bodo's original idptr_callback commit too. It Thanks for the info! Take care, Ger turns out easier to fix threadid relative to what was pre-0.9.9 than to hack it on top of existing stuff. So the first CRYPTO_THREADID attempt is gone, but I won't revert Bodo's

Logging mechanism in OpenSSL Library

Hi, Is there any kind of logging mechanism in OpenSSL. My requirement is as follows: I have a proxy which links with OpenSSL library to handle HTTPS request and responses. Now I need to log messages relating to the handshake process. Is there any kind of logging mechanism in OpenSSL library

Re: [PATCH] PURIFY and valgrind

Leave everything as all zero's; that will make it real obvious not to use this in production code. #ifdef PURIFY memset(buf, 0, num); memset(md_c, 0, sizeof md_c); memset(local_md, 0, sizeof local_md); #endif -- STSM, DataPower Chief Programmer WebSphere

Re: [PATCH] PURIFY and valgrind

On Thu, Jul 17, 2008 at 7:07 PM, Frederic Heem [EMAIL PROTECTED] wrote: Please find attached a patch which makes valgrind and friends happy. Some changes had been done in md_rand.c which broke the purpose of PURIFY. Needless to say that the define PURIFY is *not* for production system...

Re: [PATCH] PURIFY and valgrind

On Friday 18 July 2008 10:57:50 Bodo Moeller wrote: On Thu, Jul 17, 2008 at 7:07 PM, Frederic Heem [EMAIL PROTECTED] wrote: Please find attached a patch which makes valgrind and friends happy. Some changes had been done in md_rand.c which broke the purpose of PURIFY. Needless to say that

Re: [PATCH] PURIFY and valgrind

On Fri, Jul 18, 2008 at 6:00 PM, Geoff Thorpe [EMAIL PROTECTED] wrote: On Friday 18 July 2008 10:57:50 Bodo Moeller wrote: On Thu, Jul 17, 2008 at 7:07 PM, Frederic Heem [EMAIL PROTECTED] wrote: Please find attached a patch which makes valgrind and friends happy. Some changes had been done

[PATCH] PURIFY and valgrind, 2nd round

Hi, The previous patch didn't fully work due a mysterious valgrind issue (something related to loading libssl multiple time through dl_open). This patch is simply what has Robert suggested. By the way, can someone explain me why some uninitialized static variables are used create a random

Re: [PATCH] PURIFY and valgrind, 2nd round

Debian c suffered from simply removing all calls to seed the random number generator with enough entropy to make it secure. When it comes to entropy, every little bit helps. The calls to add uninitialized static variable locations are never relied upon to seed the PRNG with enough entropy, but

RE: [PATCH] PURIFY and valgrind

Agreed, though where possible it's preferable for PURIFY-handling to simply not use the uninitialised data at all, rather than initialising it before use. (NB, I know this yields the same quality result, but appearances in the code are often as important as the outcome of the executable -