sorry for my poor english...
memory management is widely provided by various platforms, but seem some
embedded enviornment RTOS don't provide the ordernary memory library we
usually used.
recently, i try to porting openssl onto an NO_STDIO platform which doesn't
provided malloc, realloc, ...etc.
as i trace the code of openssl, i find that by the hard work of openssl
develpment teams there are only few place that really calling these
function. so we can easy redirect it to the library that os provided or
self-implemented.
i migrate gmalloc (GNU malloc) as the memory management for openssl,
although i haven't fully test about it, but recently it works fine on
/crypto/bn, bio, rand, dh. (still under testing)
cause i am new in security, and embeded field, hope it useful to you.
if there's a better solution, please let us know
best rgds.
Mars Lin
Broadband Networks
DELTA NETWORKS, INC.
-----Original Message-----
From: Nathan Bell [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 21, 2001 6:01 AM
To: OpenSSL Users; [EMAIL PROTECTED]
Subject: drop-in memory management
There is already support for drop-in cryptography, but doing drop-in
memory management seems like a more highly applicable feature. After
already having done this I realize that it is not a daunting task. It
would've been even better had there been documentation pointing to which
files to change.
Does anyone else see this as a good future feature?
Note to openssl-dev listees:
I'm not on this list, so could you please CC [EMAIL PROTECTED]
when you reply?
--
Nathan Bell
Companion Corporation
Evelyn Manufacturing
801-943-7277
Etc...
><));>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
