tree dc761b2a50ab9d9f34d0f08551c9117e1b26ae5e
parent 33e799fe192ed38b83508f8bf6f4b732878327e1
author David Benjamin <davidben@chromium.org> 1418982737 -0500
committer Adam Langley <agl@google.com> 1422297670 +0000

Disable NPN and Channel ID in DTLS.

They're not in the duplicated handshake state machines anyway. But we still
shouldn't negotiate them. d1_pkt.c assumes Finished is the only post-CCS
handshake message. An unexpected handshake message in the current epoch may
either be a retransmit/out-of-order message from the previous handshake, or a
message from the next handshake (also potentially out-of-order). In the former
case, we shouldn't spin up another handshake state machine instance.

(This assumption is required due to a protocol bug. DTLS resets sequence
numbers after a handshake, so it is necessary to categorize handshake fragments
by pre-CCS and post-CCS to distinguish between retransmit and renego.)

Change-Id: Ib3c1c7085c729e36a40f7ff14494733156924a24
Reviewed-on: https://boringssl-review.googlesource.com/3028
Reviewed-by: Adam Langley <agl@google.com>