| commit | fb260748aec1840e879eb5b986838fffe3a22620 | [log] [tgz] |
|---|---|---|
| author | Bob Beck <bbe@google.com> | Mon Jul 24 14:29:34 2023 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 24 22:06:09 2023 +0000 |
| tree | a2a94fffbdb5a40ef66baf0126da8701636e6d32 | |
| parent | 7cb91d23cdb25f9f084c13941c2ca78fc50cc9d1 [diff] |
Sync pki to chromium aef592bb1b83f019c8342bbc2c476758ccb6098d Adds general_names and crl unittests to pki tests, with associated data files for crl unittest. Bug: chromium:1322914 Change-Id: Idda8e4a98ef3744a76717db32628db554c12e415 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/61965 Auto-Submit: Bob Beck <bbe@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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: