Re: TLS session resume concurrency?

2005-02-16 Thread Victor Duchovni
On Fri, Feb 11, 2005 at 11:31:16AM -0500, Tim Dierks wrote: > On Thu, 10 Feb 2005 15:59:04 -0500, Victor Duchovni > <[EMAIL PROTECTED]> wrote: > > If the symmetric cypher is fully re-keyed when sessions are resumed > > while avoiding the fresh start PKI overhead, then life is simple > > and sessio

Re: TLS session resume concurrency?

2005-02-16 Thread Tim Dierks
On Thu, 10 Feb 2005 15:59:04 -0500, Victor Duchovni <[EMAIL PROTECTED]> wrote: > If the symmetric cypher is fully re-keyed when sessions are resumed > while avoiding the fresh start PKI overhead, then life is simple > and sessions can be re-used unmodified. Otherwise I may need to > ponder on desig

Re: TLS session resume concurrency?

2005-02-16 Thread Eric Rescorla
Victor Duchovni <[EMAIL PROTECTED]> writes: > If multiple processes (or threads) have access to a shared TLS session > cache, does the cache need N sessions to serve N threads? Or can (I > think unlikely if sessions resume stream-ciphers from internal state > in the cache) the same session be used

TLS session resume concurrency?

2005-02-10 Thread Victor Duchovni
If multiple processes (or threads) have access to a shared TLS session cache, does the cache need N sessions to serve N threads? Or can (I think unlikely if sessions resume stream-ciphers from internal state in the cache) the same session be used by multiple clients? Postfix only has one TLS sess