|author||David Benjamin <firstname.lastname@example.org>||Wed Apr 17 17:38:52 2019 -0500|
|committer||Adam Langley <email@example.com>||Thu Apr 18 18:37:36 2019 +0000|
Disable the common name fallback on *any* SAN list. This aligns with the Go crypto/x509 behavior and reduces the cases when the SAN to CN fallback occurs. If the certificate is new enough to have a SAN list, even if it only contains email or IP addresses, it is reasonable to assume the certificate is new enough that the common name is not a DNS name. Update-Note: Our certificate verification is getting slightly stricter. Change-Id: I9e3466d8dd8a722405c546181a589f797efa43f9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35647 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: