commit | 6ce77afa91bc0db1897cba8ce08188c804f908b1 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Nov 23 16:40:19 2022 -0500 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 09 02:25:55 2022 +0000 |
tree | cd3c8a172b0800ed82abc71b311a9f13003e115b | |
parent | faac9aa3349f149cd433582c31020d49090a0737 [diff] |
Unexport X509V3_NAME_from_section and fix the type of chtype. X509_NAME_add_entry_by_txt and friends all use int for MBSTRING_* constants. X509V3_NAME_from_section was the odd one out in using unsigned long. Bug: 516 Change-Id: Ib0bca46a080a791d2fba0b515a47b047c0777260 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/55456 Commit-Queue: Bob Beck <bbe@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: