| commit | 707af294a8af53160bd94c1dc788f8587092d997 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Mar 10 17:47:18 2017 -0500 |
| committer | Adam Langley <agl@google.com> | Sat Mar 11 00:05:29 2017 +0000 |
| tree | a8d294bd30eb7ef34d4a38887a2ac638a5499cd3 | |
| parent | 4c341d0299c9eef218a5e7219d0b12da0d88dd42 [diff] |
Support asynchronous ticket decryption with TLS 1.3. This shuffles a bit of the code around session resumption in TLS 1.3 to make the async point cleaner to inject. It also fills in cipher and tlsext_hostname more uniformly. Filling in the cipher on resumption is a no-op as SSL_SESSION_dup already copies it, but avoids confusion should we ever implement TLS 1.3's laxer cipher matching on the server. Not filling in tlsext_hostname on resumption was an oversight; the relevant check isn't whether we are resuming but whether we have a fresh SSL_SESSION to fill things into. Change-Id: Ic02eb079ff228ce4a4d3e0de7445e18cd367e8b2 Reviewed-on: https://boringssl-review.googlesource.com/14205 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: