| commit | 2b8415e8ff324cd4a322670a5a1b6cb8906ebcfd | [log] [tgz] |
|---|---|---|
| author | Steven Valdez <svaldez@google.com> | Thu Jun 30 13:27:23 2016 -0400 |
| committer | David Benjamin <davidben@google.com> | Fri Jul 01 19:01:33 2016 +0000 |
| tree | 48b12efcca80cc72a424f69848095a613685cfe0 | |
| parent | 0ba87732c659b92cbf879c09e18b8ae1f33422f0 [diff] |
Move the Digest/Sign split for SignatureAlgorithms to a lower level. In order to delay the digest of the handshake transcript and unify around message-based signing callbacks, a copy of the transcript is kept around until we are sure there is no certificate authentication. This removes support for SSL_PRIVATE_KEY_METHOD as a client in SSL 3.0. Change-Id: If8999a19ca021b4ff439319ab91e2cd2103caa64 Reviewed-on: https://boringssl-review.googlesource.com/8561 Reviewed-by: David Benjamin <davidben@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: