| commit | 4186b711f46cb353fa18dd06ea424bb452f8d310 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jun 16 20:40:18 2016 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Jun 20 17:26:02 2016 +0000 |
| tree | 48fab6faab3bd615f64412e4ffa2aec4773879c3 | |
| parent | 0407e76daae3d78d850867ed4ba66c1f7bcb4fe5 [diff] |
Don't bother storing the cofactor. It's always one. We don't support other kinds of curves with this framework. (Curve25519 uses a much simpler API.) This also allows us to remove the check_pub_key_order logic. Change-Id: Ic15e1ecd68662b838c76b1e0aa15c3a93200d744 Reviewed-on: https://boringssl-review.googlesource.com/8350 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.
There are other files in this directory which might be helpful: