|author||David Benjamin <firstname.lastname@example.org>||Fri Aug 12 15:12:29 2022 -0400|
|committer||Boringssl LUCI CQ <email@example.com>||Fri Aug 12 20:12:43 2022 +0000|
Add X509_V_FLAG_NO_CHECK_TIME. This was added in OpenSSL 1.1.0. cryptography.io binds it. They don't actually use it, but this is a useful feature to have anyway. Projects like Envoy currently implement such a mode with X509_STORE_set_verify_cb, which is a very problematic API to support. Add this so we can move them to something more sustainable. Change-Id: Iaff2d08daa743e0b5f4be261cb785fdcd26a8281 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/53965 Commit-Queue: Adam Langley <firstname.lastname@example.org> Auto-Submit: David Benjamin <email@example.com> Reviewed-by: Adam Langley <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: