There is no pre-existing way to write out all the SSL state so that another process can reconstruct it.
I would do it this way; when a connection comes in, spawn stunnel to handle the SSL with a pipe() back to the dispatcher. Use raw read on the pipe; when it's time to spawn a client, hand the pipe descriptors off to the client. This replaces the SSL problem with process-management, which if you don't find it simpler, is certainly better understood by more people. I don't remember the details of how to do this on windows, but the concept is the same. -- SOA Appliances Application Integration Middleware ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
