| commit | 384d0eaf1930af1ebc47eda751f0c78dfcba1c03 | [log] [tgz] |
|---|---|---|
| author | Steven Valdez <svaldez@google.com> | Tue Nov 06 10:45:36 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Nov 06 19:04:48 2018 +0000 |
| tree | 07240432812c76ed9c0a151552735bebc0b78efd | |
| parent | ffbf95ad41086b116111aea9404230f56fd19311 [diff] |
Make SSL_get_current_cipher valid during QUIC callbacks. Update-Note: This effectively reverts https://boringssl-review.googlesource.com/4733, which was an attempt at a well-defined story during renegotiation and pre-handshake. This is a behavior change, though one that matches OpenSSL upstream. It is also more consistent with other functions, such as SSL_get_curve_id. Renegotiation is now opt-in, so this is less critical, and, if we change the behavior mid-renegotiation, we should do it consistently to all getters. Change-Id: Ica6b386fb7c5ac524395de6650642edd27cac36f Reviewed-on: https://boringssl-review.googlesource.com/c/32904 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: