| commit | f71036e4e3eab25272719120234884bf11ab7a12 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jan 21 14:49:39 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jan 27 23:23:57 2017 +0000 |
| tree | aa4702de0d89f9b227d4682e3333dadc8515c469 | |
| parent | 1a444daca6da74ad748c681dd3aa5a5d283b1e43 [diff] |
Remove ssl_hash_message_t from ssl_get_message. Move to explicit hashing everywhere, matching TLS 1.2 with TLS 1.3. The ssl_get_message calls between all the handshake states are now all uniform so, when we're ready, we can rewire the TLS 1.2 state machine to look like the TLS 1.3 one. (ssl_get_message calls become an ssl_hs_read_message transition, reuse_message becomes an ssl_hs_ok transition.) This avoids some nuisance in processing the ServerHello at the 1.2 / 1.3 transition. The downside of explicit hashing is we may forget to hash something, but this will fail to interop with our tests and anyone else, so we should be able to catch it. BUG=128 Change-Id: I01393943b14dfaa98eec2a78f62c3a41c29b3a0e Reviewed-on: https://boringssl-review.googlesource.com/13266 Reviewed-by: David Benjamin <davidben@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: