|author||David Benjamin <email@example.com>||Mon Sep 05 01:23:54 2022 -0400|
|committer||Boringssl LUCI CQ <firstname.lastname@example.org>||Wed Sep 14 23:05:22 2022 +0000|
Unexport CONF_parse_list. This doesn't seem to be used anywhere and unexporting it lets us make it size_t-clean. Update-Note: CONF_parse_list was removed. If parsing strings, use a dedicated string library. Bug: 516 Change-Id: I86fb353bb95268f7234fddf5563ecf2a27da99bd Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54468 Commit-Queue: David Benjamin <email@example.com> Reviewed-by: Bob Beck <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: