| commit | 75f9914e1783ea0ef0191434e4aa00ae5abde4be | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Nov 12 12:36:06 2016 +0900 |
| committer | Adam Langley <agl@google.com> | Tue Nov 15 18:18:39 2016 +0000 |
| tree | 941205e042dda9b2f165ba2308978bacda3d7247 | |
| parent | 1e21e994ecf359bc3c220838fd5227724cf1ffc6 [diff] |
Align TLS 1.2 and 1.3 server session validity checks. Having that logic in two different places is a nuisance when we go to add new checks like resumption stuff. Along the way, this adds missing tests for the ClientHello cipher/session consistency check. (We'll eventually get it for free once the cipher/resumption change is unblocked, but get this working in the meantime.) This also fixes a bug where the session validity checks happened in the wrong order relative to whether tickets_supported or renew_ticket was looked at. Fix that by lifting that logic closer to the handshake. Change-Id: I3f4b59cfe01064f9125277dc5834e62a36e64aae Reviewed-on: https://boringssl-review.googlesource.com/12230 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: