| commit | c1e156ae16fa8b61af9b5d2b74e59d3f86e141be | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jan 08 18:15:40 2021 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 19 23:23:20 2021 +0000 |
| tree | 1845622d517abcab447fea7259abeb46d98c5e73 | |
| parent | a9319d9b0f5d9cfe01ffd00ac926af86485dc981 [diff] |
Add DH_compute_key_padded. OpenSSL has a fixed-width version of DH_compute_key nowadays. Searching around callers of DH_compute_key, many of them go back and re-pad the secret anyway. Uses of DH should migrate to modern primitives but, in the meantime, DH_compute_key_padded seems worthwhile for OpenSSL compatibility and giving fixed-width users a function to avoid the timing leak. Bump BORINGSSL_API_VERSION since one of the uses is in wpa_supplicant and they like to compile against a wide range of Android revisions. Update-Note: No compatibility impact, but callers that use DH_compute_key and then fix up the removed leading zeros can switch to this function. Then they should migrate to something else. Change-Id: Icf8b2ace3972fa174a0f08ece39710f7599f96f2 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45004 Commit-Queue: David Benjamin <davidben@google.com> 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.
Project links:
There are other files in this directory which might be helpful: