|tagger||Adam Langley <firstname.lastname@example.org>||Mon Jul 30 15:45:15 2018 -0700|
|author||Adam Langley <email@example.com>||Thu Jul 19 10:03:56 2018 -0700|
|committer||Adam Langley <firstname.lastname@example.org>||Mon Jul 30 15:44:53 2018 -0700|
Fix the build with FIPS + NO_ASM. Setting OPENSSL_NO_ASM skips enabling the “ASM” language in CMake. However, the FIPS module fundamentally needs to build asm because delocate works via textual assembly. Thus this combination is currently broken with CMake. This change ensures that support for building asm is enabled in CMake for this combination. Change-Id: I4516cf3a6f579ee7c72f04ac25d15785926cf125 Reviewed-on: https://boringssl-review.googlesource.com/29884 Reviewed-by: Adam Langley <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: