Work around a GCC false positive warning GCC is getting upset about working off of the first in.size() bytes of out, but in.size() is at most kBlockSize, so this definitely fits. Still, moving the Span(out).first(in.size()) call slightly earlier seems to silence this, probably by causing the compiler to emit the bounds check slightly earlier. The bounds check is redudant (it's a consequence of the compiler not knowing some of the bounds), but if we're paying for it anyway, may as well pay for it before we call f_final than after. That seems to, as a side effect, make GCC behave. Fixed: 496903323 Change-Id: Ia7a5279964d78d3998658d44cbbb06f9ea544f19 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/91807 Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@google.com> Presubmit-BoringSSL-Verified: Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Lily Chen <chlily@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: