| commit | 492c9aa90c97db64fd044898ae0b2a3efccef10e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Aug 31 16:35:22 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Sep 06 18:12:11 2018 +0000 |
| tree | e98410c43de6d8bdecc2505e7a79157e883761f9 | |
| parent | e84c375303341c769620daf969d128f383b3e303 [diff] |
Fill in a fake session ID for TLS 1.3. Historically, OpenSSL filled in a fake session ID for ticket-only client sessions. Conscrypt relies on this to implement some weird Java API where every session has an ID and may be queried out of the client session cache and, e.g., revoked that way. (Note that a correct client session cache is not keyed by session ID and indeed this allows one server to knock out another server's sessions by matching session IDs. But existing APIs are existing APIs.) For consistency between TLS 1.2 and TLS 1.3, as well as matching OpenSSL's TLS 1.3 implementation, do the same in TLS 1.3. Note this smooths over our cross-version resumption tests by allowing for something odd: it is now syntactically possible to resume a TLS 1.3 session at TLS 1.2. It doesn't matter either way, but now a different codepath rejects certain cases. Change-Id: I9caf4f0c3b2e2e24ae25752826d47bce77e65616 Reviewed-on: https://boringssl-review.googlesource.com/31525 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: