tree 3d726fbfa4262f74104a82f3553b13724f6174ce
parent 9ac494a171014fa0f06dbf2b0e08abf1d7ec85aa
author David Benjamin <davidben@google.com> 1729811113 -0400
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> 1730224060 +0000

runner: Flush DTLS fragments on key change in our 1.3 test stack

Our test DTLS stack buffered up fragments in order to pack or reorder
them. On key change, we need to write the fragments out, but since this
was written for DTLS 1.2, we did so on ChangeCipherSpec writes. DTLS 1.3
does not use ChangeCipherSpec.

The only reason this worked at all was that middlebox compatibility mode
inserted fake ChangeCipherSpecs and we actually haven't yet made BoGo
stop sending them at DTLS 1.3! Fix that too.

(We'll probably want an option to send them again and test how our stack
reacts... once we decide whether that is to reject them or ignore them.
https://boringssl-review.googlesource.com/c/boringssl/+/69947 only
handled not sending them.)

Bug: 42290594
Change-Id: Ie406e4caefd163ffbb0b82191400a9549999f4ee
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72449
Reviewed-by: Nick Harper <nharper@chromium.org>
Commit-Queue: David Benjamin <davidben@google.com>