|author||David Benjamin <email@example.com>||Mon Jun 13 11:47:31 2022 -0400|
|committer||Boringssl LUCI CQ <firstname.lastname@example.org>||Tue Aug 02 23:33:50 2022 +0000|
Rework STACK_OF(T) documentation. Rather than documenting the private sk_new_null, etc., APIs and then expecting callers to infer the real API, describe a real sample API under #if 0. Also rename the function pointers to sk_FOO_whatever, which both matches OpenSSL and reduces the namespaces we squat. The generic callback types I've renamed to OPENSSL_sk_whatever, to similarly match OpenSSL. We should also rename plain sk_whatever, but that'll require fixing some downstream code. Bug: 499 Change-Id: I49d250958d40858cb49eeee2aad38a17a63add87 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/53009 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: David Benjamin <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: