Erik de Castro Lopo wrote:
Wow, I didn't know about most of those functions.
Calling these is a vast improvement but there are still a small
leak. Here's is the one and only valgrind report after doing:
I may not have recited all of the available cleanup functions maybe
there are more.
Maybe the problem is the confusing and non-obvious naming conventions.
* Developers should be forced to call initilization code before using
any part of the library (no implicit init).
* Any initilization code should have an accompanying cleanup function
following some arbitrary naming convention.
At the moment there is a patchwork of components each with differing
schemes (explicit or implicit initialization) and the cleanup functions
you need to use aren't an obvious naming choice in relation to the
init() function you called. So you have a right to be confused.
Would it help to have a function named something like
SSL_library_release() that basically calls the above functions
one by one?
The complexity arises from that fact that OpenSSL has a number of
independant modules, some of which are built on top of other modules.
The problem is that its perfectly acceptable for the same application to
use SSL functions and HASH/Cryptographic functions independently.
If you are cleaning up after all OpenSSL usage has been finished then
for process termination then thats less of a problem then maybe this
concern is not one you will have.
Darryl
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
