|author||Bob Beck <firstname.lastname@example.org>||Wed Nov 22 17:37:31 2023 -0700|
|committer||Boringssl LUCI CQ <email@example.com>||Fri Dec 08 19:19:35 2023 +0000|
Remove fillins/log.h In the test code we simply use std::cerr instead of LOG, this then removes some of the DVLOG from path_builder that seem inappropriate to send as debugging information to the delegate. (Alternatively we could keep them and deal with the DVLOG define in this file if we really wanted to keep these) Bug: 668 Change-Id: I323f7a896999f279d0d6af5b73c7e1d132c07f3b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/64170 Reviewed-by: David Benjamin <firstname.lastname@example.org> Commit-Queue: David Benjamin <email@example.com> Auto-Submit: 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: