|author||David Benjamin <email@example.com>||Thu Nov 28 08:32:16 2019 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Mon Dec 02 22:14:18 2019 +0000|
Allocate small TLS read buffers inline. Our TLS read patterns are always read(5); read(record_size); read(5); read(record_size); ...;. Allocate the 5-byte reads inline in SSLBuffer. This avoids bouncing on a 5-byte malloc to learn a socket is idle and avoids calling malloc twice on each record. This costs a few bytes but means we malloc once per record, rather than twice per record + once each time the state machine is run while idle. Change-Id: I4f6dafe4141cbb890b921a5fa8d528c1fb98a0b4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39004 Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: Adam Langley <email@example.com>
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: