| commit | 0f5d7d3f042a9ab5b9cf63534a1b1de5396a4fe8 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Mar 27 10:15:15 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Mar 27 16:37:53 2017 +0000 |
| tree | 976ca2f4981f9b06c2d033c14358ec1d41340429 | |
| parent | 95321e15f299d4f9b023831eaa868feee4fe9c0b [diff] |
Just allocate what's needed for SSL write buffers. When we refactored all the buffering logic, we retained upstream OpenSSL's allocation patterns. In particular, we always allocated fixed size write buffer, even though, unlike when reading, we trivially know a tighter bound (namely however much we happen to be writing right now). Since the cutoff for when Windows' malloc starts having a hard time is just below the TLS maximum record size, do the more natural thing of allocating what we need to hold outgoing ciphertext. (This only does anything to the write half. Read half is a bit more involved.) BUG=chromium:524258 Change-Id: I0165f9ce822b9cc413f3c77e269e6154160537a7 Reviewed-on: https://boringssl-review.googlesource.com/14405 Reviewed-by: Steven Valdez <svaldez@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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: