| commit | f04976ba254a909e8f94ffdf2e18ad50a0580560 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Oct 07 00:37:55 2016 -0400 |
| committer | Adam Langley <agl@google.com> | Sun Oct 09 17:19:24 2016 +0000 |
| tree | e8e343f9e8eb410a1a6890a419b8d5bfaaecb65d | |
| parent | 9d0b4bcb9245eeb00139f746f842d78650859337 [diff] |
Remove the get_peer_groups parameter to tls1_get_grouplist. It's weird and makes things more confusing. Only use it for local preferences as there is a default. Peer preferences can be read directly. Also simplify the logic for requiring a non-empty peer group list for ECDHE. The normal logic will give us this for free. Change-Id: I1916155fe246be988f20cbf0b1728380ec90ff3d Reviewed-on: https://boringssl-review.googlesource.com/11527 Reviewed-by: Adam Langley <agl@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: