| commit | 4fe3c90b7d781d4075ad23c49afc568b5881f10a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Aug 16 02:17:03 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Sep 19 20:35:35 2016 +0000 |
| tree | 958dc9e9e002e1fefcd1cadb2224eb72c739fb53 | |
| parent | 3ba2ae0417a814f5fb2cdc64b61a47d5266e270f [diff] |
Release TLS 1.3 key shares earlier in TLS 1.2. This isn't hugely important since the hs object will actually be released at the end of the handshake, but no sense in holding on to them longer than needed. Also release |public_key| when we no longer need it and document what the fields mean. Change-Id: If677cb4a915c75405dabe7135205630527afd8bc Reviewed-on: https://boringssl-review.googlesource.com/10360 Reviewed-by: Steven Valdez <svaldez@google.com> 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: