| commit | 9a85565ed3ea8cff359bcd39d4679939694df598 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <[email protected]> | Tue Nov 26 11:13:07 2024 -0500 |
| committer | Boringssl LUCI CQ <[email protected]> | Tue Nov 26 20:03:44 2024 +0000 |
| tree | 75bc6fadd7dab22a136fe23c273b145d5bb1b63c | |
| parent | 705a80f6955bf1fa63572dbc4e0729e698c1d9db [diff] |
Don't access the read_buffer directly in read_v2_client_hello I missed a spot in https://boringssl-review.googlesource.com/21865. The function is passed an input span and should just work with that span. This does the exact same thing rigth now in == read_buffer.span() right now. But we'll want this if we ever add a bytes-in/bytes-out API. Change-Id: Ie12ad783b77b78335beba3a27da4d205ec828077 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73547 Commit-Queue: Bob Beck <[email protected]> Auto-Submit: David Benjamin <[email protected]> Reviewed-by: Bob Beck <[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: