| commit | be9a86f459f8e785bac42abcea5d13bd4ded251e | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Thu Feb 18 09:04:34 2021 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Feb 18 18:32:41 2021 +0000 |
| tree | 3189a61796053afc744cd996cb530c02a0ddba6d | |
| parent | bbd1742f6176c5eadb44ccf36c78a86ce0543bc2 [diff] |
Revert "Revert "Disable check that X.509 extensions implies v3."" This reverts commit 4251d0d3f66a182e1b1ff22e9d0085613a1253ec, except that the reland dates have been updated to not be in the past. Change-Id: I7812c0e36d87ed1e049ec0a7d92a23efec881a81 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45704 Commit-Queue: David Benjamin <davidben@google.com> 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.
Project links:
There are other files in this directory which might be helpful: