| commit | db638238d29708a20b991af3b2488e45a8bbcf71 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 26 14:29:07 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 26 12:13:51 2025 -0700 |
| tree | 567d8ae03a8e2480fd348ff2fe002564a5413759 | |
| parent | 2375765eeae11c78eec8c6bf1bdfa53cf86e6ef8 [diff] |
Tolerate nullptr in i2d_X509_NAME This used to be tolerated by way of the general tasn_enc machinery. We don't support this, but one existing test was relying on this to force i2d_X509_NAME to fail and exercise that error path. I don't think it's actually possible, short of malloc failure, to construct an X509_NAME such that i2d_X509_NAME fails anymore. It's easier to just restore this artificial failure case than to figure out what, if anything, to do with their check. Change-Id: I49bd19e711518756c5ff20230dc4df6c56bf1977 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82310 Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@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: