Matt Caswell 4e8548e80e Introduce the recv_max_early_data setting ... Previoulsy we just had max_early_data which controlled both the value of max early_data that we advertise in tickets *and* the amount of early_data that we are willing to receive from clients. This doesn't work too well in the case where we want to reduce a previously advertised max_early_data value. In that case clients with old, stale tickets may attempt to send us more early data than we are willing to receive. Instead of rejecting the early data we abort the connection if that happens. To avoid this we introduce a new "recv_max_early_data" value. The old max_early_data becomes the value that is advertised in tickets while recv_max_early_data is the maximum we will tolerate from clients. Fixes #6647 Reviewed-by: Paul Dale <paul.dale@oracle.com> (Merged from https://github.com/openssl/openssl/pull/6655)		2018-07-06 09:26:39 +01:00
..
internal	Remove __cplusplus preamble from internal headers	2018-06-22 12:24:59 +02:00
openssl	Introduce the recv_max_early_data setting	2018-07-06 09:26:39 +01:00