[gnutls-devel] [TLS] multiple clients in one process (was: Re: Deployment ... Re: This working group has failed)

Nico Williams nico at cryptonector.com
Mon Dec 2 00:13:33 CET 2013

Another thing you can do if you're really concerned about unload is to tell
the link-editor/RTLD to not unload the GnuTLS object(s), or dlopen()
yourself at self-init time and purposefully leak the handle.  It's ok to
leak a small, *fixed* amount of resources.  In particular it's far more
important to support the layered plugin use case, including racing callers
in different objects, than to not leak anything on last dlclose().

(There is something to lose from not being unloadable randomized load
addresses changing over the life of one process, but it'd be nice to have
an existence proof that real apps with long-running processes actually
unload add reload modules.)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20131201/2f8fa88e/attachment.html>

More information about the Gnutls-devel mailing list