| commit | fc02b59b27e449467b91143449be8602417dc31b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Feb 17 16:26:01 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Feb 17 21:36:37 2017 +0000 |
| tree | 0dced5f7b0e2d80f155534ffe93e1562be245081 | |
| parent | 45738dd496030f8d8e92387b7f0781ce23b8df17 [diff] |
Move tmp.extended_master_secret to SSL_HANDSHAKE. The two non-trivial changes are: 1. The public API now queries it out of the session. There is a long comment over the old field explaining why the state was separate, but this predates EMS being forbidden from changing across resumption. It is not possible for established_session and the socket to disagree on EMS. 2. Since SSL_HANDSHAKE gets reset on each handshake, the check that EMS does not change on renego looks different. I've reworked that function a bit, but it should have the same effect. Change-Id: If72e5291f79681381cf4d8ceab267f76618b7c3d Reviewed-on: https://boringssl-review.googlesource.com/13910 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@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: