commit | b65e630ec060b36d713c640df22db99a5ed045ee | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Apr 06 17:55:21 2020 -0400 |
committer | Adam Langley <agl@google.com> | Tue Apr 07 20:54:45 2020 +0000 |
tree | 2b58c51eae3d5a43a3a2a4584ac934bb62cf04bb | |
parent | bd1fa86feb7de41910ed111d003fd1b49235168a [diff] |
Move BN_nnmod calls out of low-level group_set_curve. group_set_curve is called when instantiating the built-in curves and when creating arbitrary curves. The former has non-NULL BN_CTXs and fully reduced inputs. Move the logic for this to the deprecated EC_GROUP_new_curve_GFp function so it can be dropped from most binaries. Change-Id: I5ff60d6d51acb79fbcb32588e6324a5b2627b6d2 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40544 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: