We're using the standard internal session (maintained per SSL_CTX object); not
tickets.
We're seeing that the sessions are shared, a refcount is maintained, but that
SSL does modified fields within a session while it's being used. Most notably
an address sanitizer build found the EC point stuf
On Wed, Aug 13, 2014 at 03:32:00PM -0400, Salz, Rich wrote:
> What's the programming model for using session cache with a multi-threaded
> server?
> When a client connects, a refcount on the object is incremented.
A lot depends on whether the cache is internal, or external via callbacks,
and wet
What's the programming model for using session cache with a multi-threaded
server?
When a client connections, a refcount on the object is incremented. But then
fields can be changed (such as ecpointformat). Does it make more sense for
session to deep-copy the session from the cache?
--
Princip
