| commit | 7934f08b263e31e68ba067e666268e42e8a4011d | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Aug 01 16:32:25 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Aug 08 21:13:04 2017 +0000 |
| tree | 77352381fe0b55eddb87700a672d01d3293b8a2e | |
| parent | 8f94c31b19c688692d9afcffe3afb2f85391b125 [diff] |
Replace init_msg/init_num with a get_message hook. Rather than init_msg/init_num, there is a get_message function which either returns success or try again. This function does not advance the current message (see the previous preparatory change). It only completes the current one if necessary. Being idempotent means it may be freely placed at the top of states which otherwise have other asychronous operations. It also eases converting the TLS 1.2 state machine. See https://docs.google.com/a/google.com/document/d/11n7LHsT3GwE34LAJIe3EFs4165TI4UR_3CqiM9LJVpI/edit?usp=sharing for details. The read_message hook (later to be replaced by something which doesn't depend on BIO) intentionally does not finish the handshake, only "makes progress". A follow-up change will align both TLS and DTLS on consuming one handshake record and always consuming the entire record (so init_buf may contain trailing data). In a few places I've gone ahead and accounted for that case because it was more natural to do so. This change also removes a couple pointers of redundant state from every socket. Bug: 128 Change-Id: I89d8f3622d3b53147d69ee3ac34bb654ed044a71 Reviewed-on: https://boringssl-review.googlesource.com/18806 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: