On Wed, Jun 11, 2008 at 09:08:48PM -0700, David Schwartz wrote:
>
> > I am wrapping an ssl socket using c++ and use a third party library
> > steam implementation. the library I use requires an implementation of a
> > copy constructor. I managed to dup and initialize a simple BIO and then
> > free it as required, but when it comes to SSL struct, thing don't seem
> > to work the same way.
> > BIO code:
> > used in copy constructor:
> [snip]
> > I am looking for a way to duplicate the SSL struct with all of it's
> > components in order to keep using it without a new handshake.
> > destructor is pretty straight forward, but copy/duplication is trickier.
> > this is what i got so far:
> [snip]
> > I'm lost as to what is missing here.
> > any help would be greatly appreciated.
>
> An SSL structure represents the actual connection itself. The connection
> cannot be duplicated -- there is no way to turn one connection into two
> identical connections. So what you're trying to do does not make logical
> sense.
An SSL_SESSION can be obtained from one SSL connection and used to speed up
the handshake (bypass public-key operations) for a new connection.
--
Viktor.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
