|author||David Benjamin <firstname.lastname@example.org>||Tue Oct 17 15:48:46 2017 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Wed Oct 25 03:31:56 2017 +0000|
Check early ALPN before offering 0-RTT. We enforce that servers don't send bogus ALPN values, so consumers may assume that SSL_get0_alpn_selected won't have anything terribly weird. To maintain that invariant in the face of folks whose ALPN preferences change (consider a persisted session cache), we should decline to offer 0-RTT if early_alpn would have been rejected by the check anyway. Change-Id: Ic3a9ba4041d5d4618742eb05e27033525d96ade1 Reviewed-on: https://boringssl-review.googlesource.com/22067 Commit-Queue: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.com> Reviewed-by: Steven Valdez <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: