tree 798a7d06f1de4ddf27b06f9db631c1e59bbbf28d
parent 08a932fe880d336904c52f01df4b140d71d6a5d9
author David Benjamin <davidben@google.com> 1731962952 -0500
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> 1733264801 +0000

Implement receiving KeyUpdates in DTLS 1.3

Receiving KeyUpdates is easy because as soon as you get to the message,
you can act on it. We just needed to fix up some edge cases around epoch
management.

I have included a couple tests which exercise the absolute highest
possible epoch. On my laptop, they take a couple seconds to run each
with an unoptimized shim. That is not very fast, but will maybe be
bearable. But we may need a flag later to disable those tests.

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