commit | a6124742d008e7cd4613833350a16d68537687c9 | [log] [tgz] |
---|---|---|
author | Alessandro Ghedini <alessandro@ghedini.me> | Sun Feb 24 13:05:31 2019 +0000 |
committer | Adam Langley <agl@google.com> | Wed Feb 27 17:26:07 2019 +0000 |
tree | 0de314ab0915d0d3f9e0ef852139d4b654c13a67 | |
parent | 1e0262ad872ca393e88c17e6e5c5b9abad3a36cc [diff] |
Update *_set_cert_cb documentation regarding resumption Since 34202b93b6195e9c55402a6bc2653956d0cd26d8 cert_cb is always called before resumption is checked. Change-Id: I27ca5653144027a1f545a90ecb6b68e64783a66a Reviewed-on: https://boringssl-review.googlesource.com/c/35004 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: