Namespace all lhash internal symbols. LHASH_OF is only used internally (and can later be changed to be a C++ template). As such, its symbols can just all be moved into our namespace. Here I put the entire .cc file in the namespace block, as lhash has no public symbols at all, and as it also contains structs that can't be defined in the namespace. Down from 974 to 906 unintended exported symbols. Bug: 42220000 Change-Id: I6333a8c86b185326fa88a1a0b382a3421f201699 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/86247 Commit-Queue: Rudolf Polzer <rpolzer@google.com> Reviewed-by: Xiangfei Ding <xfding@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: