|Adam Langley <firstname.lastname@example.org>
|Sun Apr 26 14:10:03 2020 -0700
|CQ bot account: email@example.com <firstname.lastname@example.org>
|Sun Apr 26 21:38:36 2020 +0000
Move fork_detect files into rand/ Files in the top-level of fipsmodule/ are considered be FIPS-support files by generate_build_files.py. However, fork_detect is different. Rather than have more special cases in the support scripts, this change moves fork_detect into fipsmodule/rand. It's not a perfect fit, and maybe it could have been its own directory, but it's not bad and fixes the build for now. Change-Id: I875088dd458069190dade870e085865e1306f55a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40964 Reviewed-by: Adam Langley <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: