|author||Brian Smith <email@example.com>||Thu Nov 12 18:31:35 2015 -1000|
|committer||Adam Langley <firstname.lastname@example.org>||Thu Nov 19 00:52:33 2015 +0000|
Fix error handling in |p256-x86_64|. This makes similar fixes as were done in the following OpenSSL commits: c028254b12a8ea0d0f8a677172eda2e2d78073f3: Correctly set Z_is_one on the return value in the NISTZ256 implementation. e22d2199e2a5cc9b243f45c2b633d1e31fadecd7: Error checking and memory leak leak fixes in NISTZ256. 4446044a793a9103a4bc70c0214005e6a4463767: NISTZ256: set Z_is_one to boolean 0/1 as is customary. a4d5269e6d0dba0c276c968448a3576f7604666a: NISTZ256: don't swallow malloc errors. The fixes aren't exactly the same. In particular, the comments "This is an unusual input, we don't guarantee constant-timeness" and the changes to |ecp_nistz256_mult_precompute| (which isn't in BoringSSL) were omitted. Change-Id: Ia7bb982daa62fb328e8bd2d4dd49a8857e104096 Reviewed-on: https://boringssl-review.googlesource.com/6492 Reviewed-by: Adam Langley <email@example.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: