Subject: Re: [TLS] More clarity on resumption and session hash

From: Adam Langley <[email-masked]>
Date: Wed, 3 Jun 2015 15:20:51 -0700

I've landed a change[1] in BoringSSL which enforces connection aborts
in three cases:
 a) as a client: a session without EMS is resumed with a ServerHello
that supports it.
 b) as a server or client: a session with EMS is resumed on a
connection without EMS negotiated.

It also causes servers not to resume sessions without EMS if the
client offers EMS in the resumption ClientHello.

Chrome will implement these behaviours in a future version and
hopefully that's enough to ensure good behaviour in the ecosystem as a
whole.

[1] https://boringssl.googlesource.com/boringssl/+/ba5934b77f0058dc963b075e0ec1f401a24c0b2b

Cheers

AGL