| commit | 5274cea40447aad76a7bb8c7c8693e9c4ee39aef | [log] [tgz] |
|---|---|---|
| author | Steven Valdez <svaldez@google.com> | Wed May 08 11:34:57 2019 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu May 23 16:11:44 2019 +0000 |
| tree | fa466ed047a61a26d1fd48098a348724300073ed | |
| parent | 35a5a9e7beddb9cec70d7bc1b70a6ac441093f87 [diff] |
Always store early data tickets. This stores early data tickets regardless of whether early data is enabled in the initial handshake, and provides an API to query whether early data would be performed to allow for comparison between early data enabled and disabled resumptions. Change-Id: Id3ef62e36b5be48f6a39fcd7c67d332b7d495141 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35964 Commit-Queue: Steven Valdez <svaldez@google.com> 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: