|author||David Benjamin <firstname.lastname@example.org>||Wed Oct 14 13:26:19 2015 -0400|
|committer||Adam Langley <email@example.com>||Mon Oct 26 20:27:28 2015 +0000|
Synchronize sha512-x86_64.pl with upstream. We missed 7eb9680ae1bf5dd9aeb61c401f2c3bd900ac9aeb. This is a no-op as we don't set shaext right now anyway. This also includes some cosmetic changes to minimize the diff with upstream. ("cosmetic". Upstream's perl doesn't like spaces.) Change-Id: I17fa663ddaa38c27854d4f59fb83960528d9ba78 Reviewed-on: https://boringssl-review.googlesource.com/6250 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: