| commit | 8fc2dc07d868efafe0f4db5a5df238e2576deb13 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Aug 22 15:07:51 2017 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Aug 23 15:58:52 2017 +0000 |
| tree | 3a412d0b87b78349d79deec6bec9c482c3bcc88d | |
| parent | e7848220a241e5bbb6b98a6f1f65e4d4f1cef308 [diff] |
Put SCTs and OCSP responses in CRYPTO_BUFFERs. They both can be moderately large. This should hopefully relieve a little memory pressure from both connections to hosts which serve SCTs and TLS 1.3's single-use tickets. Change-Id: I034bbf057fe5a064015a0f554b3ae9ea7797cd4e Reviewed-on: https://boringssl-review.googlesource.com/19584 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@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: