|author||Pete Bentley <email@example.com>||Fri Nov 08 14:34:23 2019 +0000|
|committer||Adam Langley <firstname.lastname@example.org>||Fri Nov 08 15:49:37 2019 +0000|
Conditionally define PTRACE_O_EXITKILL in urandom_test.cc On older Linux distributions (e.g. Centos 7 which we still use for Conscrypt releases) PTRACE_O_EXITKILL is defined in <linux/ptrace.h> but this can't be included alongside <sys/ptrace.h> due to conflicting defines, so this is the path of least resistance for portability. Could also define this as 0 if undefined, but all distributions seem to use 1<<20, and Centos 7 kernels should have support as they are 3.10 and later and PTRACE_O_EXITKILL was introduced around 3.8. Change-Id: Ib8a6e0dbc62613e30c38a6cc09522c2d7b92577b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38704 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: