| commit | be88fd4a09943317889c11e639b04c53bfc99ce7 | [log] [tgz] |
|---|---|---|
| author | Bob Beck <bbe@google.com> | Fri Sep 20 18:52:42 2024 +0000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 11 13:01:37 2024 +0000 |
| tree | 97225d58977862716850049e4127668c1adc6cd7 | |
| parent | 4bc2b6654271ec95863d77c27685f3f78f3c13e7 [diff] |
Add ssl_has_CA_names and ssl_add_CA_names Change-Id: I22866c72e9cacbcceb48fc7c99dd22a5ff7edeae Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71609 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Bob Beck <bbe@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: