| commit | 8422b5c7079acc0b90d644d3be9e0b441955fbf8 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jan 12 12:24:48 2026 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 12 13:25:17 2026 -0800 |
| tree | bbf92222d48d0ab6bdc94ea4ef5f0f3f682f8a1e | |
| parent | f075344a3acb2096d910e14dccbf09a4145ae429 [diff] |
Test that DTLS 1.2 rejects renegotiation We do not support renegotiation in DTLS at all. This falls out of us generically rejecting all unexpected handshake records after the handshake, but test this more explicitly. DTLS 1.2 renegotiation is particularly weird because they reset the message sequence number, which actually makes message reassembly ambiguous! One cannot *just* use the sequence number state to distinguish between retransmit of a past message and a new message. We currently assume fragments are renegotiation attempts by default, and special-case Finished as a retransmit. If we were went the other way[*], we should have a test that covers the new messages. [*] Going the other way may be a little tidier if we want to implement crbug.com/383016430. We also currently would break if we ever enabled NPN or Channel ID in DTLS. Change-Id: I9f304d0f7ea356fb67e63e22ee06d1ed0fcaa804 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/86987 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
Project links:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: