Hello, > Maybe what i've said was not clear enough. > In fact, i don't want two processes to be able to > communicate on the socket at the same time. > > I just would like the process which has accepted the > connection to give the SSL object to a second process. > Then the first process doesn't need the SSL object > anymore. If this is fork/exec model this should be no problem: parent accept() and SSL_accept() then fork(), parent SSL_free() and close() and child to some work. Of course SSL_accept() may be done in child too so parent only close() after accept().
If this processes are already created then "main" process may give accept()'ed file descriptor to "worker" for SSL_accept() by unix socket for example. Best regards, -- Marek Marcola <[EMAIL PROTECTED]> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
