| commit | 68a0b1b1122a1b8d71d033cbee82fe73d48a769a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Aug 16 13:36:57 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Aug 18 16:48:11 2017 +0000 |
| tree | 9e136ad782cf8db5fc70bea53604a74eb13ab018 | |
| parent | e2daba6d20cdf397db0fda00198d9582f9c8086a [diff] |
Remove RFC 5114 groups. These groups are terrible, we got the function wrong (unused ENGINE parameter does not match upstream), and the functions are unused. Unwind them. This change doesn't unwind the X9.42 Diffie-Hellman machinery, so the checks are still present and tested. (We can probably get rid of the X9.42 machinery too, but it is reachable from DSA_dup_DH. That's only used by wpa_supplicant and, if that code ever ran, it'd be ignored because we don't support DHE in TLS. I've left it alone for the time being.) Bug: 2 Change-Id: I8d9396983c8d40ed46a03ba6947720da7e9b689a Reviewed-on: https://boringssl-review.googlesource.com/19384 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: