Symbol renaming: also rename inline functions using `redefine_extname`. This has previously not been done as they're `static inline` in C, and using the pragma would warn. However, in that case they don't need any renaming _at all_, as they're not emitting linker symbols to begin with! Reduces public macro footprint to zero with Clang. No change with GCC. Removes inline functions from macro footprint with nonsupporting compilers such as MSVC when compiling as C. Also, rephrase `BORINGSSL_ADD_USER_LABEL_AND_PREFIX` so in case the new C identifier already has a macro on it, it will use that macro's expansion. This makes the `redefine_extname` and `#define` methods behave more similar to each other in case e.g. a global header include wants to rename our renamed symbols further. Bug: 42220000 Change-Id: I7ceade63493ead2f7859c14c1e7916306a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/91627 Commit-Queue: Xiangfei Ding <xfding@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: