Update third_party/benchmark to 1.9.5 Picks up https://github.com/google/benchmark/commit/d8db2f90b643eb28a12976beb4d57bcfb639911d This results in deprecation warnings with benchmark::internal::Benchmark so go ahead and fix those. Also add third_party/benchmark to .bazelignore. This stops `bazel test ...` from recursing in here. It looks like we previously suppressed copying some files, but we can avoid having to post-process the files this way. Change-Id: Idf20fce28153a450fe03e121d9bc0d601d43ec6c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88948 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Lily Chen <chlily@google.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: