|author||David Benjamin <firstname.lastname@example.org>||Sat Dec 03 17:45:02 2022 -0500|
|committer||Boringssl LUCI CQ <email@example.com>||Fri Dec 09 02:23:13 2022 +0000|
Finish porting dh_test.cc and ripemd_test.cc to GTest. They're the only two half-finished ports left, so we may as well finish that up and trim them down a little. Change-Id: Ic058124a44086161ab5d2d6fa24448492c3ba219 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/55506 Auto-Submit: David Benjamin <firstname.lastname@example.org> Commit-Queue: Bob Beck <email@example.com> Reviewed-by: Bob Beck <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: