| commit | b5e57d0703e83875199f48828799d30f57eb140d | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Oct 24 19:05:13 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 29 17:47:40 2024 +0000 |
| tree | 3d726fbfa4262f74104a82f3553b13724f6174ce | |
| parent | 9ac494a171014fa0f06dbf2b0e08abf1d7ec85aa [diff] |
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>
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: