| commit | 11fa70396b6fb7ab72472d4133d588362476ec91 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Apr 11 22:13:45 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Apr 13 21:23:40 2017 +0000 |
| tree | 1985ce3e0378c031520e66512d9035f844adabb4 | |
| parent | a33e0fc9320c45d68cf06d81a413559f1aa95212 [diff] |
Remove the last remnants of key_exchange_info. DHE ciphers are gone, so we no longer need to clear drop the "group_id" field there. That leaves static RSA, but: - We mass-invalidated every serialized client session in 364f7a6d21f73d099f4f80800973174a8f71e90f, long after we stopped filling in key_exchange_info on the client. - Server sessions were not mass-invalidated, but static RSA key_exchange_info never worked on the server. This means it is safe to remove this logic. Change-Id: Id43b233cca066a81686be7c056c530ba8e89f761 Reviewed-on: https://boringssl-review.googlesource.com/15005 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: Steven Valdez <svaldez@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: