|author||David Benjamin <firstname.lastname@example.org>||Sat Feb 04 11:48:59 2017 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Sat Feb 11 00:42:00 2017 +0000|
Add a helper for comparing byte strings. We compare pointer/length pairs constantly. To avoid needing to type it everywhere and get GTest's output, add a StringPiece-alike for byte slices which supports ==, !=, and std::ostream. BUG=129 Change-Id: I108342cbd2c6a58fec0b9cb87ebdf50364bda099 Reviewed-on: https://boringssl-review.googlesource.com/13625 Reviewed-by: David Benjamin <email@example.com> Commit-Queue: David Benjamin <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: