| commit | 2044181e01261b2790dc83a5cc6bbc40e61f4385 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Sun Feb 04 11:20:14 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Feb 05 02:03:29 2018 +0000 |
| tree | c12e64871091630e5d807098e18623a13af65705 | |
| parent | a3123910509c5ae5f8b8475bdeed1944a5a42fab [diff] |
Set output point to the generator when not on the curve. Processing off-curve points is sufficiently dangerous to worry about code that doesn't check the return value of |EC_POINT_set_affine_coordinates| and |EC_POINT_oct2point|. While we have integrated on-curve checks into these functions, code that ignores the return value will still be able to work with an invalid point because it's already been installed in the output by the time the check is done. Instead, in the event of an off-curve point, set the output point to the generator, which is certainly on the curve and hopefully safe. Change-Id: Ibc73dceb2d8d21920e07c4f6def2c8249cb78ca0 Reviewed-on: https://boringssl-review.googlesource.com/25724 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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: