|author||Adam Langley <firstname.lastname@example.org>||Fri Oct 18 08:52:38 2019 -0700|
|committer||Adam Langley <email@example.com>||Fri Oct 18 20:37:54 2019 +0000|
Add sanity checks to FIPS module construction. If -ffunction-sections or -fdata-sections is enabled when doing a FIPS shared build, the linker script won't do what's expected and will silently end up including very little (or nothing) in the integrity check. This changes alters the linker script to discard any text or data sections other than the main one, which should make this failure much more obvious. Also, add assertions (that are always enabled) in the module to check that a few obvious things that should be inside the module boundaries actually are. Change-Id: I91178e213a28a7c0c4a38155974e452cd9d558d1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38324 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: