| commit | 4e41926774f2d1ab3a56610d5bcf6833642a1299 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Nov 07 15:45:53 2016 -0500 |
| committer | Adam Langley <agl@google.com> | Wed Nov 09 17:02:33 2016 +0000 |
| tree | eb4b94e1864c32ed4ab45bf8688f514d04561798 | |
| parent | 54955fe7111ebef568bf986b4bb60b090598ad31 [diff] |
Move key_block into SSL_HANDSHAKE. This is already manually released at the end of the handshake. With this change, it can happen implicitly, and SSL3_STATE shrinks further by another pointer. Change-Id: I94b9f2e4df55e8f2aa0b3a8799baa3b9a34d7ac1 Reviewed-on: https://boringssl-review.googlesource.com/12121 Reviewed-by: Adam Langley <agl@google.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: