inject_hash: Add an option to hash a different object from what we rewrite This allows us to build the FIPS module in a flow where: 1. We generate a bcm.o, which still has some link-time relocations inside BCM, they're just link-independent 2. We link bcm.o into *some* arbitrary sample executable or shared object, bcm_relocated 3. We sample the hash out of bcm_relocated and write it back into bcm.o Bug: 362530616, 469788763 Change-Id: Ia6ce5667e2ea5d28adf6fc33cdf9e2b0875fb589 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/85927 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: