On Wed, Jun 25, 2014 at 11:15 AM, Jens Maus <m...@jens-maus.de> wrote: > ... > > Actually, I now understand that I can keep a single SSL_CTX throughout the > whole lifetime of my application and just assign it to the SSL_new() call. > However, as I outlined in my last posts, if I change my code like this I run > into the verify_callback problem and that I have to be able to specify > different app_data pointers per SSL connection or otherwise I cannot store > the certificate check results for evaluation by my application. > The SSL* should be unique per connection. Is it not possible to keep a data structure somewhere that uses the SSL* as a key? Then stuff the data as the value of the pair.
I know there's a difference between connections and sessions (one connection can have multiple sessions; sessions can be resumed, etc). So I'm not clear if it will meet all your needs. Jeff ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
