tree 3248d7f7e912bc6a5662b91a1660ad53d3818e22
parent 197a654639aa39a86782b06abebdeccbfa197e2b
author David Benjamin <davidben@google.com> 1729788926 -0400
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> 1730171905 +0000

Remove now redundant check for extra DTLS messages in epoch 1

This dates to
https://boringssl-review.googlesource.com/c/boringssl/+/8988, which was
several iterations back of the message read API. We now catch extra
Finished by way of:

In DTLS 1.2, there is no key change at the end of the handshake:

- If the fragment was received before the handshake was over, we queue
  it up and then the handshake makes sure incoming messages are clear
  before completing.

- If the fragment was received after the handshake was over, we reject
  almost all handshake fragments post-handshake. (This will need to be
  rejiggered.

In DTLS 1.3, there is a key change at the end of the handshake

- If the fragment was received before the handshake was over, key
  changes require incoming messages are clear and we reject it.

- If the fragment was received after the handshake was over, we
  currently do not notice. We do not retain the old epoch and just drop
  the record. (This is fine, since we won't actually process it.) But
  when we implement DTLS 1.3 key changes properly, we might end up
  picking it up.

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