commit | 7f7bd6b559a80caead7d8574a3e92f1e5adbf941 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Mar 23 14:00:44 2018 -0400 |
committer | David Benjamin <davidben@google.com> | Thu Mar 29 15:50:25 2018 -0400 |
tree | e2a43a408106812cad551eb57938c5a576f3ad55 | |
parent | 8df8e64205d0f8334ee4d403306bfcd4287004b0 [diff] |
Fix typo in point_add. Rather than writing the answer into the output, it wrote it into some awkwardly-named temporaries. Thanks to Daniel Hirche for reporting this issue! Bug: chromium:825273 (cherry picked from commit 5fca61391822252baf3dc37529ba02f6d7611acf) Change-Id: I315087f5e7414118a6f70bf4aed76325aa4f76a0
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: