Sorry, I do not have the idea what you mean? What is the OpenSSL memory handler?
If I was unclear: OpenSSL doesn't call the memory handling functions (malloc, realloc, free) direct.
It uses memory allocate functions (OPENSSL_malloc(), OPENSSL_realloc() and OPENSSL_free())
With CRYPTO_set_mem_functions() you can set the internally used memory handling functions and become OpenSSLs master do decide if and where new memory will be allocated...
But you can overwrite the OpenSSL memory handler. Create an new one that has an (thread specific) flag to indicate if the data should reside in the shared memory. Now every time you do SSL data, you set the flag and the SSL data will be allocated in the shared memory...
Bye
Goetz
-- DMCA: The greed of the few outweighs the freedom of the many
smime.p7s
Description: S/MIME Cryptographic Signature
