From: Nathan Bell <[EMAIL PROTECTED]>
nbell> There is already support for drop-in cryptography, but doing drop-in
nbell> memory management seems like a more highly applicable feature. After
nbell> already having done this I realize that it is not a daunting task. It
nbell> would've been even better had there been documentation pointing to which
nbell> files to change.
nbell> Does anyone else see this as a good future feature?
Actually, there is such a thing, but admitedly not documented. You
can create your own allocator and deallocator functions and hook them
in using the function CRYPTO_set_mem_functions(). See crypto.h
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-733-72 88 11
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, GemPlus: http://www.gemplus.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
