|author||Pete Bentley <email@example.com>||Fri Sep 20 20:29:05 2019 +0100|
|committer||Adam Langley <firstname.lastname@example.org>||Mon Sep 23 15:50:35 2019 +0000|
Add page protection logic to BCM self test. On Android only, assume code is compiled for Execute-only memory, so add Read permission for the duration of the self test and then mark the pages Execute-only again. NB if libcrypto is not compiled for Execute-only memory, then attempting to change the page permissions to PROT_EXEC at the start of the self test does not cause it to fail, however changing it to PROT_NONE does. Bug: 134580074 Test: m && flashall Test: Manual tests described above. Change-Id: Ibbf8405a5a9b162ce26532127aaf62c539cd9163 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37644 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: 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: