| commit | 1a08739634fa4f2c4a9dc7ead983fbe7b8b3cf2e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Oct 10 11:56:45 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 10 09:14:01 2025 -0700 |
| tree | f0dbf84c16a78226ac2678591e3b49f2803b8515 | |
| parent | 08cca1f2241245a058138469aacdb7a1587182d3 [diff] |
Document that ASN1_STRING_set_by_NID enforces the bounds on the string This then impacts X509_NAME_ENTRY_set_data, which impacts X509_NAME_ENTRY_create_by_OBJ, which impacts X509_NAME_ENTRY_create_by_NID. It is... unfortunate that you need to follow so many links in the docs to find out what these functions do, but they're all so absurdly complicated, with layered quirks, it was difficult to keep all those copies in sync without just referencing each other. (This came up in discussion of cl/817621459.) Change-Id: I399f1f3a2734e8fa67fe92166e3984e5a2e091e7 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82748 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Lily Chen <chlily@google.com> Commit-Queue: Lily Chen <chlily@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: