Enable most of the prefixed builds that work. The win32 shared library builds are all not working yet and staying disabled. Let's keep them compile_only though - this should suffice for prefixing purposes and won't take _too_ long. NOT enabling these on CQ (but do enabling on CI): - android_aarch64 (we'd learn nothing that's not already covered by android_arm and mac_arm64) - ios64 (we'd learn nothing that's not already covered by mac_arm64 - linux_clang (we'd learn nothing that's not already covered by linux and win64_clang) - mac (we'd learn nothing that's not already covered by mac_arm64 and linux) Bug: 42220000 Change-Id: I330a56f9d47bdd84feec76d34357746c6a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88288 Commit-Queue: Xiangfei Ding <xfding@google.com> Auto-Submit: 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: