|David Benjamin <firstname.lastname@example.org>
|Wed Apr 12 16:28:25 2017 -0400
|Adam Langley <email@example.com>
|Wed Apr 12 22:42:28 2017 +0000
Ensure consumers set up include paths properly. In some cases, consumers may include a BoringSSL header without setting up include paths. This risks pulling in system OpenSSL headers instead. For almost every BoringSSL header, the first #include is base.h, which does not exist upstream, thus the mistake will be caught. The exception is base.h itself which naturally does not include itself. Have it include an empty is_boringssl.h header to catch this mistake. Change-Id: Ia96586ecc627ff46867d8af8b68138185866f074 Reviewed-on: https://boringssl-review.googlesource.com/14949 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: