commit | e7681d1a788d31a30b714b9688b29074645b096d | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Jul 04 16:59:11 2022 -0400 |
committer | Adam Langley <agl@google.com> | Wed Jul 06 23:12:58 2022 +0000 |
tree | 64f64e3704ed60f7d52da7bd6b06263a2f9c986e | |
parent | 28c5354806248f9882eba0a8ad8d63c436018037 [diff] |
Rewrite scalar operations in spake25519.c with BN_ULONG This reuses code we already have, and also avoids another union. Bug: 301 Change-Id: I2f4ab564cf220818ca96d9c99a122c1e5cdc9e7a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/53228 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: