| commit | 114cebdacb57c71c3c22cd559d4465fb766fbf23 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <[email protected]> | Fri Nov 01 20:59:54 2024 -0400 |
| committer | Boringssl LUCI CQ <[email protected]> | Tue Nov 12 16:21:36 2024 +0000 |
| tree | d00923fcecb560c78d1d583e5f0473ea09c14020 | |
| parent | b52cbd2466bc1cc4d3f00d33dcac74a4372f9469 [diff] |
runner: ACK flights in DTLS 1.3 by default Tests can override this behavior if they want. This required fixing up some logic around tracking lastRecordInFlight. We implicitly assumed that, by the time we're ready to write, there's nothing more to read in the current record. But BoringSSL currently sends a single record with two NewSessionTickets in it, even though they're nominally two flights. Instead, only wipe the state if the packet is empty. There's probably a better way to process this, but this will do. Bug: 42290594 Change-Id: Ib22d575777eb6866dbc02b9ba3b74e8d61a74b6c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72847 Reviewed-by: Nick Harper <[email protected]> Commit-Queue: David Benjamin <[email protected]>
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: