| commit | bd1fa86feb7de41910ed111d003fd1b49235168a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Apr 06 14:34:09 2020 -0400 |
| committer | Adam Langley <agl@google.com> | Tue Apr 07 20:28:59 2020 +0000 |
| tree | 10e53ac1aeb68c44ce34468f510f920bb28d4e2c | |
| parent | 243a29241ca582a6e47bb5caa193be12cf8890f9 [diff] |
Clean up various EC inversion functions. This fixes two issues. First, we have been lax about whether the low-level inversion functions fail on zero input or output zero. Fix the documentation and call the latter inv0 or inverse0 to match the terminology used in draft-irtf-cfrg-hash-to-curve. (Although we may not actually need inv0 given the optimization in D.2.) This has no actual effect because the functions were only used in contexts where the inputs were already guaranteed to be non-zero. Still, we should be consistent here. Second, ec_scalar_inv_montgomery and ec_scalar_inv_montgomery_vartime claim to perform the same operation, but they do not. First, one computed inv0 and the other computed inv (except only in some implementations, so fix it to be consistent). Second, the former computes inverses in the Montgomery domain, while the latter converts to the Montgomery domain and then inverts. Rename it to ec_scalar_to_montgomery_inv_vartime, which is... questionably understandable but at least looks different. Change-Id: I9b4829ce5013bdb9528078a093f41b1b158df265 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40526 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: