| commit | 1902d818ac4fef9497dfe5d0ce6f2c99f585bdff | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Fri Mar 23 11:40:45 2018 -0700 |
| committer | Adam Langley <agl@google.com> | Fri Mar 30 16:50:11 2018 +0000 |
| tree | f4e862e384369b572c4e2480f488eefc605d1798 | |
| parent | 56f5eb9ffdebedc70b6be11e0c4aa0a36a029537 [diff] |
Tighten and test name-checking functions. This change follows up from e759a9cd with more extensive changes and tests: If a name checking function (like |X509_VERIFY_PARAM_set1_host|) fails, it now poisons the |X509_VERIFY_PARAM| so that all verifications will fail. This is because we have observed that some callers are not checking the return value of these functions. Using a length of zero for a hostname to mean |strlen| is now an error. It also an error for email addresses and IP addresses now, and doesn't end up trying to call |strlen| on a (binary) IP address. Setting an email address with embedded NULs now fails. So does trying to configure an empty hostname or email with (NULL, 0). |X509_check_*| functions in BoringSSL don't accept zero lengths (unlike OpenSSL). It's now tested that such calls always fail. Change-Id: I4484176f2aae74e502a09081c7e912c85e8d090b Update-Note: several behaviour changes. See change description. Reviewed-on: https://boringssl-review.googlesource.com/26764 Reviewed-by: David Benjamin <davidben@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.
There are other files in this directory which might be helpful: