| commit | e1e78130f51288d65be0b43eebbe13385068980f | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Tue Jan 31 15:24:31 2017 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Feb 01 00:24:24 2017 +0000 |
| tree | b84d171a9d308a2a172927b3a9d656aab148da88 | |
| parent | 7cd0a978cc3cbfe771b6fdecdcb83ceaf09cf4a6 [diff] |
Keep a reference to |X509|s appended to a chain. The recent CRYPTO_BUFFER changes meant that |X509| objects passed to SSL_CTX_add_extra_chain_cert would be |free|ed immediately. However, some third-party code (at least serf and curl) continue to use the |X509| even after handing over ownership. In order to unblock things, keep the past |X509| around for a while to paper over the issues with those libraries while we try and upstream changes. Change-Id: I832b458af9b265749fed964658c5c34c84d518df Reviewed-on: https://boringssl-review.googlesource.com/13480 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: