| commit | 9c0f22cdfbb696bcba8cbf02ae5737df15aae704 | [log] [tgz] |
|---|---|---|
| author | Bob Beck <bbe@google.com> | Thu Jun 29 11:18:37 2023 -0600 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 29 21:03:13 2023 +0000 |
| tree | f9d2e29e5065bdec77423f4826cad63115c16e2d | |
| parent | 28e4a1b838b2ffbf9e2151ae5fcfffe5ab0ffac0 [diff] |
Sync pki to chrome 28e4a1b838b2ffbf9e2151ae5fcfffe5ab0ffac0 While we are at it, add a fillins/log.h and modify import_spec.json to remove the need for patching out LOG and DVLOG (which removes one more patch in the patch stack Change-Id: I3b7b512490ee0e8c465734b2236b31da7d132ec7 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/61225 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: 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: