| commit | 56d280da2fc04a818744ec2a8622424905ee4a02 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Aug 03 14:29:19 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Aug 03 21:43:50 2016 +0000 |
| tree | 3b9b626716a21c80426c9b88edb8dc2060b6eaa0 | |
| parent | 057b678dca96eb0754beb083a04a10177747ff6d [diff] |
Remove the SSL_R_SESSION_ID_CONTEXT_UNINITIALIZED sanity check. While the sanity check isn't insane (one should arrange for sessions to be invalidated once client auth settings change, and a sid_ctx is one way to do it), this check lives in a poor place to enforce configuration mistakes. To be effective, it needs to happen at the start of the handshake, independent of the ClientHello from the peer. But the benefit this check gives is low compared to the trouble it will be to continually maintain this difference from OpenSSL (our own ssl_test and bssl_shim forget to set a dummy sid_ctx). Instead, remove it so we don't have to duplicate it across TLS 1.2 and TLS 1.3. Also so we don't have weird failures which only manifest once a resuming client connects. Change-Id: Ia7f88711701afde5e26b7782c2264ce78dccc89b Reviewed-on: https://boringssl-review.googlesource.com/9112 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: