| commit | d24a38200fef19150eef00cad35b138936c08767 | [log] [tgz] |
|---|---|---|
| author | Bob Beck <bbe@google.com> | Tue Sep 26 17:06:37 2023 -0600 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 27 02:13:00 2023 +0000 |
| tree | 4c3fc515dfb8509fe01bb5f0009056e9a9d56797 | |
| parent | 764e6a319ba97dc36a8523583488c315ff22c4ae [diff] |
Sync pki to chromium eddbcb143c7462e0b8d60e859b96d678ca0c013c This removes one more patch, and adapts import to deal with gmock from chrome which is now included in boring. Bug: chromium:1322914 Change-Id: I2a5957f741252941fea76205a21e98fd655f8cae Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/63225 Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: 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: