| commit | 276b7e81273528e3936ce4e3fc3cea9324c68254 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jan 21 14:13:39 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jan 27 23:15:52 2017 +0000 |
| tree | 61062af91c19f6455a81c74b77a0ec8f3dec77e0 | |
| parent | 6f07d726c91d4df5c62e1ea985e780daa383f076 [diff] |
Move optional message type checks out of ssl_get_message. This aligns the TLS 1.2 state machine closer with the TLS 1.3 state machine. This is more work for the handshake, but ultimately the plan is to take the ssl_get_message call out of the handshake (so it is just the state machine rather than calling into BIO), so the parameters need to be folded out as in TLS 1.3. The WrongMessageType-* family of tests should make sure we don't miss one of these. BUG=128 Change-Id: I17a1e6177c52a7540b2bc6b0b3f926ab386c4950 Reviewed-on: https://boringssl-review.googlesource.com/13264 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: