commit | c03c2181901fe44e0eec700aaf645769ea2d240a | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Sep 20 16:34:34 2017 -0400 |
committer | David Benjamin <davidben@google.com> | Wed Sep 20 21:06:00 2017 +0000 |
tree | a8f136cca216383c2c8431215dc33a8a0b826952 | |
parent | 4015000e19e876f54867b656ceb96702aeb31c9b [diff] |
Fix some issues with name constraints test certs. First, I spelled the wildcard name constraint in many_constraints.pem wrong. It's .test, not *.test for name constraints. (This doesn't matter for some_names*.pem, but it does to avoid a false negative in many_names3.pem.) Second, the CN of certs should be a host, not "Leaf". OpenSSL 1.1.0 checks "host-like" CNs against name constraints too and "Leaf" is host-like. I've also made the generator deterministic and checked it in, as PEM blobs are not reviewable. Change-Id: I195d9846315168a792cca829aff25c986339b8f5 Reviewed-on: https://boringssl-review.googlesource.com/20584 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: