|author||David Benjamin <firstname.lastname@example.org>||Thu Jun 16 13:58:28 2022 -0400|
|committer||Boringssl LUCI CQ <email@example.com>||Wed Jun 22 20:07:32 2022 +0000|
clang-format remaining directories. Previously, we did not clang-format a few directories because we had left them largely untouched. clang-format them now so we're finally more uniform. This CL is the result of the following commands: for d in asn1 x509 x509v3 pem; do clang-format -i crypto/$d/*.h clang-format -i crypto/$d/*.c done (Written in this funny way because crypto/pem/*.h doesn't match anything.) Change-Id: I7f4ca9b3a9c8f07d6556e00e9e84b3c0880ee12e Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/53085 Commit-Queue: Bob Beck <firstname.lastname@example.org> Reviewed-by: Bob Beck <email@example.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: