Re: [TLS] Security concerns around co-locating TLS and non-secure

[Michael D'Errico <[e-mail]>]

Martin Rex wrote:
> 
> Trying to load off server state on the client as a TLS session cookie
> might not be a solution for many scenarios, because it is simply not
> available in many implementations and the server-side state might
> be "huge" whereas the communication frequency and message size
> might be tiny -- which easily results in a _magnitude_ higher load
> when switching from HTTP to HTTPS.

I guess it depends on what you consider "huge."  My server issues
session tickets that are between about 230 and 260 bytes.  If a
client certificate is negotiated, then this figure rises due to
the fact that the certificate needs to be included in the ticket,
but nobody uses them anyway (not trying to start a war :-)

Mike