|author||David Benjamin <email@example.com>||Fri Aug 12 15:33:43 2022 -0400|
|committer||Boringssl LUCI CQ <firstname.lastname@example.org>||Fri Aug 12 20:13:43 2022 +0000|
Add X509_STORE_CTX_set0_trusted_stack. OpenSSL renamed X509_STORE_CTX_trusted_stack to X509_STORE_CTX_set0_trusted_stack. This name is a partially an improvement as this is a setter, and partially a setback. The "set0" name is a bit misleading. set0 is narrowly correct, in that this function does not adjust refcounts. But usually set0 functions don't adjust refcounts because they take ownership of the input. This function does not. It simply borrows the pointer and assumes it will remain valid for the duration of X509_STORE_CTX. OpenSSL also renamed X509_STORE_CTX_set_chain to X509_STORE_CTX_set0_untrusted. I've declined to add that one for now, in hopes that we can remove both functions. From what I can tell, there's no point in ever using either function. It's redundant with the last parameter to X509_STORE_CTX_init. Change-Id: I0ef37ba56a2feece6f927f033bdcb4671225dc6f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/53966 Reviewed-by: Adam Langley <email@example.com> Auto-Submit: David Benjamin <firstname.lastname@example.org> Commit-Queue: 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: