| commit | 95f79606901e64c1d494a4b786350e2287cf8fa7 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat May 03 14:40:34 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 07 10:45:59 2025 -0700 |
| tree | 843485ec720c30b167e07a2360d9f525fb21b1b0 | |
| parent | 60c7f790009c142ab0ddb92a568300e82e3da628 [diff] |
Also add BIO_meth_get_write and BIO_meth_get_read The Folly library has also fallen to this folly and uses these functions to even get at read/write hooks (although they then replace them). These are the problem ones that will break if the library ever moves to size_t-clean hooks, but so it goes. When we go to size_t-clean these functions, we can just make int-based ones just for these broken APIs to return. Bug: 412269080 Change-Id: I9def3d67cb751b2a85c00527d63231983f0f02c4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79047 Reviewed-by: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@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: