|author||David Benjamin <firstname.lastname@example.org>||Wed Oct 11 23:55:18 2017 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Fri Oct 27 02:38:45 2017 +0000|
Clear no-op BN_MASK2 masks. This is an OpenSSL thing to support platforms where BN_ULONG is not actually the size it claims to be. We define BN_ULONG to uint32_t and uint64_t which are guaranteed by C to implement arithemetic modulo 2^32 and 2^64, respectively. Thus there is no need for any of this. Change-Id: I098cd4cc050a136b9f2c091dfbc28dd83e01f531 Reviewed-on: https://boringssl-review.googlesource.com/21784 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: