| commit | e60b080dda138e1dd02d99fb34641ac22e46c85d | [log] [tgz] |
|---|---|---|
| author | Pete Bentley <prb@google.com> | Thu Sep 12 15:43:12 2019 +0100 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Sep 12 15:45:49 2019 +0000 |
| tree | 73321fe3c95d3323ca1962b7ab64681aefc29dff | |
| parent | 5ce7022394055e183c12368778d361461fe90a6e [diff] |
Only write self test flag files if an environment variable is set. Prevents arbitrary processes linked against libcrypto, which run before the self test binaries, from triggering SELinux audit logs. Fails safe. I.e. default is not to write a flag file which in turn will mean all processes loading libcrypto run a full set of KAT tests until the variable is set. Alternative considered: Use a weak gloabl symbol containing the flag (defaulting to "don't write") and override in the self test binaries. However at the very least this would need to be in a separate object file other than bcm.o to prevent local symbol resolution, so unsure if that would be acceptable. Change-Id: I32b20699bdd7ecaff06fc5f79b213d9a9d5f6253 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37404 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.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.
Project links:
There are other files in this directory which might be helpful: