|author||Adam Langley <firstname.lastname@example.org>||Thu Mar 22 10:02:54 2018 -0700|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Mar 22 17:19:07 2018 +0000|
Support the OpenSSL “pass zero for strlen” when setting X.509 hostnames. BoringSSL does not generally support this quirk but, in this case, we didn't make it a fatal error and it's instead a silent omission of hostname checking. This doesn't affect Chrome but, in case something is using BoringSSL and using this trick, this change makes it safe. BUG=chromium:824799 Change-Id: If417817b997b9faa9963c09dfc95d06a5d445e0b Reviewed-on: https://boringssl-review.googlesource.com/26724 Commit-Queue: Adam Langley <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.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: