|author||Adam Langley <email@example.com>||Wed Aug 21 14:27:23 2019 -0700|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri Aug 23 00:20:22 2019 +0000|
Add self-test suppression flag file for Android FIPS builds. FIPS IG 9.11 allows for a shared library to skip running self tests if they have already run successfully for a given module and environment. This change has Android FIPS builds read and write a flag file in /dev/boringssl to implement this. The flag file is named after the hash of the module to ensure specificity. Change-Id: I5c4e7b6244831746e61c5f78f703b0b4fb0ddd10 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37204 Reviewed-by: Adam Langley <firstname.lastname@example.org> Reviewed-by: David Benjamin <email@example.com> Commit-Queue: 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: