Title: Does anyone know how to get Apache to link libssl statically?
Does anyone know how to get libtool to link libssl statically into Apache (apr) for mod_ssl?
I am trying to get to the point where when I do: # ldd httpd
The libssl.so.x does not show up as a shared library.
Any help i
I agree with closing the issue - I believe the session caching problem
is in mod_ssl
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Geoff Thorpe
via RT
Sent: Wednesday, March 24, 2004 9:45 AM
To: Avery, Ken
Cc: [EMAIL PROTECTED]
Subject: [openssl.org
Title: RE: Major memory leak in OpenSSL using threads
0.9.7b – I will upgrade to 0.9.7d and run
tests.
From: Diarmuid O'Neill
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004
10:15 AM
To: [EMAIL PROTECTED]
Cc: Avery,
Ken
Subject: RE: Major memory leak in
OpenSSL
I have narrowed it down to the function BN_BLINDING_new in
the file crypto\bn\bn_blind.c, the memory allocated for the BN_BLINDING
structure never gets freed. I am assuming that the BIGNUM structures allocated
with BN_new inside of BN_BLINDING never gets freed also.
Here are my test res
Title: Memory leak in Apache/mod_ssl/OpenSSL
After tagging the OPENSSL_malloc/CRYPTO_malloc memory allocation calls and running tests over the weekend calls to OPENSSL_malloc in the following files failed to release memory by calling the corresponding OPENSSL_free:
bn_bind.c - 494,788 outsta
I have been working on this problem a couple months now and
could really use some advice.
The problem basically manifests when you turn OpenSSL
caching on and the leak is very substantial – multiples of 8k, megabytes
per day.
I realize this could be mod_ssl misbehaving.
Does any
Title: There appears to be a major memory leak in mod_ssl/OpenSSL
After conducting several tests is appears there is a major memory leak in mod_ssl/OpenSSL when using either the worker (Linux) or mpm_winnt (Windows) MPM modules.
I have been tracking this down for a couple of weeks and though
Title: Testing
