tree fc006c9ff97249e723305e95aaeac6a268bf74da
parent a0b324f96615bdca7bd048f23589a2445ccdc6a4
author David Benjamin <davidben@google.com> 1727206674 -0400
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> 1727986517 +0000

Use the same EVP_AEADs for TLS and DTLS

The funny AEADs enforce that the outgoing sequence numbers monotonically
increase, which is true for DTLS too. This is one less is_dtls boolean
to plumb.

When we first added this in
https://boringssl-review.googlesource.com/c/boringssl/+/16625, it didn't
work for DTLS because it checked the nonce started at zero, and our
DTLS 1.2 nonce construction (matching what ultimately ended up in the
DTLS 1.2 ChaCha20-Poly1305 ciphers) uses the combined epoch + seqnum.

But then https://boringssl-review.googlesource.com/c/boringssl/+/25384
made the AEAD check for any monotonically increasing sequence, so it's
perfectly DTLS-compatible.

Change-Id: I8e2e21527db85c682f2f4bd590d174f9015fcd35
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71567
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>