Pregenerate: restructure console output. Sample: ``` Use of Clang has been disabled via -clang= flag. Not generating symbol lists. The following tasks have been skipped: - prefix_symbols: 2 The following tasks have succeeded: - README: 1 - err_data: 1 - perlasm: 158 - prefix_symbols_internal: 4 - sources: 5 ``` Also route all logging through the log package instead of using stderr directly. The previous "spam" can be enabled via `-v` if needed. Bug: 478905604 Change-Id: I8050b0e44a970913fc45d53d7d7f3e676a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88588 Reviewed-by: Xiangfei Ding <xfding@google.com> Commit-Queue: 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: