| commit | 352740cef428f0f1eccdfff8dca9aaf1f85e31e4 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Dec 25 18:24:41 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 23 22:46:09 2024 +0000 |
| tree | 1bfb7e60773bc28c257922f13dd8aa3cea01e503 | |
| parent | becb3ffccdecff83047285ebea20e5b85b2d65b1 [diff] |
Document and test X509_PURPOSE and X509_TRUST machinery The trust and purpose is all a bit tied up together, as is the meaning of the certificates in an X509_STORE at all. (It's hard to discuss whether a "trusted certificate" is actually a trust anchor without a description of trust settings to reference.) Cut the Gordian Knot by documenting all that first. Later CLs will move other symbols into the sections established here. Also as the behavior is a little complex, add some tests to cover some of this machinery. Bug: 426 Change-Id: Idde8bc4e588de92ebabf6ecf640b62a2a6803688 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65207 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: