| commit | fe5f7c7b56e1d54478d2983c26153ead80e0322a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Sat Dec 19 20:54:07 2015 -0500 |
| committer | Adam Langley <agl@google.com> | Tue Dec 22 23:29:21 2015 +0000 |
| tree | c68a3e72c32890e81a74e55a6dcd88fbd2d2e2ba | |
| parent | 0d56f888c3f748f276249e0733acfc31851a9443 [diff] |
Only reserve EVP_MAX_MD_SIZE for the Finished, not twice of it. EVP_MAX_MD_SIZE is large enough to fit a MD5/SHA1 concatenation, and necessarily is because EVP_md5_sha1 exists. This shaves 128 bytes of per-connection state. Change-Id: I848a8563dfcbac14735bb7b302263a638528f98e Reviewed-on: https://boringssl-review.googlesource.com/6804 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: