| commit | a031b61230a0f19a5e34acc3874528d804b181c7 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Oct 11 20:48:25 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Oct 17 21:19:31 2017 +0000 |
| tree | b08b7351e9c0949c099fbbcd6b29048f3c534280 | |
| parent | e8d0746b88621962d8e4959f0fd8130c18932bb5 [diff] |
Replace open_close_notify with open_app_data. While a fairly small hook, open_close_notify is pretty weird. It processes things at the record level and not above. Notably, this will break if it skips past a TLS 1.3 KeyUpdate. Instead, it can share the core part of SSL_read/SSL_peek, with slight tweaks to post-handshake processing. Note this does require some tweaks to that code. Notably, to retain the current semantics that SSL_shutdown does not call funny callbacks, we suppress tickets. Change-Id: Ia0cbd0b9f4527f1b091dd2083a5d8c7efb2bac65 Reviewed-on: https://boringssl-review.googlesource.com/21885 Commit-Queue: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@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: