| commit | af0739fc737a0651bfec6c6c2164e6e98c7c2cbd | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jan 09 10:03:02 2023 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 29 00:29:21 2023 +0000 |
| tree | c8aebaf60398f3480386fe8e1172893f1ec128f9 | |
| parent | 97d48dbeb8010365a1d5cb029bee29617261d8a0 [diff] |
Const-correct sk_FOO_cmp_func This is a double-pointer and both layers should be const. This matches OpenSSL 1.1.1, so in addition to being more const-correct, we're more OpenSSL-compatible. Update-Note: Anything that defines a comparison function would need to fix the type signature. I found only one external caller, Envoy, that defines it. https://github.com/envoyproxy/envoy/pull/25051 fixes it. (That we hadn't run into the upstream incompatibility suggests this is just not a feature folks use outside the library much.) Bumping BORINGSSL_API_VERSION, in case I missed any, and there's some caller where we can't just use C++14 generic lambdas to smooth it over. Fixed: 498 Change-Id: I8f07ff42215172aa65ad8819acf69b63d6d8e54c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/56190 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com> 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:
There are other files in this directory which might be helpful: