|author||David Benjamin <email@example.com>||Sun Oct 03 22:47:13 2021 -0400|
|committer||Adam Langley <firstname.lastname@example.org>||Tue Oct 05 17:57:43 2021 +0000|
Fold x509_vfy.h into x509.h. The two headers already circularly import each other, and even have to inspect each others' header guards to manage this. Keeping them separate does not reduce include sizes. Fold them together so their header guards are more conventional. Bug: 426 Change-Id: Iaf96f5b2c8adb899d9c4a5b5094ed36fcb16de16 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/49770 Reviewed-by: Adam Langley <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: