|author||David Benjamin <email@example.com>||Wed Aug 09 15:02:34 2017 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Wed Aug 09 19:13:15 2017 +0000|
Tidy up handshake digest logic. Use SSL_SESSION_get_digest instead of the lower level function where applicable. Also, remove the failure case (Ivan Maidanski points out in https://android-review.googlesource.com/c/337852/1/src/ssl/t1_enc.c that this unreachable codepath is a memory leak) by passing in an SSL_CIPHER to make it more locally obvious that other values are impossible. Change-Id: Ie624049d47ab0d24f32b405390d6251c7343d7d6 Reviewed-on: https://boringssl-review.googlesource.com/19024 Commit-Queue: David Benjamin <firstname.lastname@example.org> Commit-Queue: Steven Valdez <email@example.com> Reviewed-by: Steven Valdez <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.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: