|author||David Benjamin <email@example.com>||Sun Jan 06 03:49:46 2019 +0000|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Wed Jan 09 03:35:55 2019 +0000|
Move aes_nohw, bsaes, and vpaes prototypes to aes/internal.h. This is in preparation for adding ABI tests to them. In doing so, update delocate.go so that OPENSSL_ia32cap_get is consistently callable outside the module. Right now it's callable both inside and outside normally, but not in FIPS mode because the function is generated. This is needed for tests and the module to share headers that touch OPENSSL_ia32cap_P. Change-Id: Idbc7d694acfb974e0b04adac907dab621e87de62 Reviewed-on: https://boringssl-review.googlesource.com/c/34188 Commit-Queue: Adam Langley <firstname.lastname@example.org> 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: