commit | 4902598935fa7d59ece8fcf8e4ed9ed2980b2b51 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Sep 19 21:24:29 2018 -0700 |
committer | Adam Langley <agl@google.com> | Thu Sep 20 14:57:36 2018 +0000 |
tree | 988fba45339241275c1e9a5180710b20ea7cb215 | |
parent | 371305f58ac47a98d32f30a9edc6fafa72e842be [diff] |
Remove SHA384_Transform from sha.h. This function doesn't actually exist. (If it did, it would be the same as SHA512_Transform. We currently omit SHA224 and SHA384's low-level transform functions.) Change-Id: Ia9d3d7c86e8f70fd5e4f13b8de4f08440dccbdcb Reviewed-on: https://boringssl-review.googlesource.com/32064 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: