| commit | e40882e848fdc03e31f974bbad6825f6886a5a38 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Dec 22 10:55:47 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 03 22:54:05 2024 +0000 |
| tree | 2358b6459620732c3a10b7ee8b56bcef1a5ca624 | |
| parent | c1c7f0929f18fabc74004242d3e4ce03f54511d0 [diff] |
Make configure_callback in x509_test.cc take the X509_STORE_CTX No change to tests, but makes it easier to test X509_STORE_CTX-level features. Change-Id: I26a02ce51b4970aedce06f64d4ebef0dba154597 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65052 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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:
There are other files in this directory which might be helpful: