|author||Adam Langley <email@example.com>||Thu May 09 16:39:49 2019 -0700|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Thu May 30 19:03:16 2019 +0000|
Add FIPS shared mode. This change adds a FIPS integrity check using shared libraries. Unlike with the static case, a shared build can take advantage of the linker resolving relocations and thus doesn't need delocation. It does mean that both .text and .rodata sections need to be handled, however, so the hashing format is slightly different. inject-hash.go is updated to be able to rewrite shared libraries to inject the correct hash value. Change-Id: I9a71910cd6df3a85e4efac896b0913e65b5f875b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36024 Commit-Queue: Adam Langley <firstname.lastname@example.org> Reviewed-by: David Benjamin <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: