Hi, there.

I have searched the archives, Google groups and Google web and can't find
any info about this problems.

If a server process issues the SSL_accept and communicates a few lines
with a client, and then decides to fork off a child process and let the
child continue with the communication, how can this be done?

I have looked into the child doing a SSL_renegotiate + SSL_handshake, but
can't get it to work. SSL_handshake locks up after SSL_renegotiate returns
0. Can I place the SSL object in shared memory, or something?

The client's SSL code is exactly the same (initialization etc) as the
parent, except the child does SSL_renegotiate+SSL_handshake instead of
SSL_accept.

1- What does an SSL capable client have to do in order to continue
   communicating using a file descriptor passed from its parent?

2- What can the parent do to resume communicating on the same fd
   after the child dies?

Any help is greatly appreciated!

Andy

--
Andreas Aardal Hanssen
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to