|author||David Benjamin <email@example.com>||Mon Dec 04 16:31:32 2017 -0500|
|committer||Adam Langley <firstname.lastname@example.org>||Mon Dec 04 21:39:54 2017 +0000|
Update tools. The newer clang should hopefully fix the new linux_clang_cfi bot. Note the VS2017 revision actually went backwards due to https://chromium.googlesource.com/chromium/src/+/db45606398cf4389bf332b0cdcffd04e7de4a4f6 Change-Id: Icaca7a57596f063ccca490917d4b78813f2e9537 Reviewed-on: https://boringssl-review.googlesource.com/23824 Reviewed-by: Adam Langley <email@example.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.
There are other files in this directory which might be helpful: