| commit | 68e7124ddf3680302650b7c10cccdef039a72202 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Mon Dec 12 11:06:16 2016 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 13 17:28:25 2016 +0000 |
| tree | a30d60e2d3e066b2e73ddf07ff739f641befbec0 | |
| parent | 364f7a6d21f73d099f4f80800973174a8f71e90f [diff] |
Hold certificates in an SSL_SESSION as CRYPTO_BUFFERSs as well. This change adds a STACK_OF(CRYPTO_BUFFER) to an SSL_SESSION which contains the raw form of the received certificates. The X509-based members still exist, but their |enc| buffer will alias the CRYPTO_BUFFERs. (This is a second attempt at https://boringssl-review.googlesource.com/#/c/12163/.) BUG=chromium:671420 Change-Id: I508a8a46cab89a5a3fcc0c1224185d63e3d59cb8 Reviewed-on: https://boringssl-review.googlesource.com/12705 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: