| commit | e3aba378c9cf7b7cbf4774fe9f8f9b8eb299692e | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Mon Apr 23 11:56:21 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Apr 23 19:21:01 2018 +0000 |
| tree | 4a050c630c138d2d074d4650ac6b1eb005514a04 | |
| parent | a2938719a4cfb5935f8332d0ca868001d0fc9bab [diff] |
Fix typo in ssl_cert_cache_chain_certs. After e325c3f4712b23de688d2eea7d7549b65a610605, this typo bites and causes SSL_CTX_get_extra_chain_certs to return an empty stack. Change-Id: I6aa7093d1ca4f3ba0f520a644b14de5b3a3ccaa6 Reviewed-on: https://boringssl-review.googlesource.com/27604 Commit-Queue: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: