rust: bssl-tls: Change context method access into shared Context methods, which is a bag of vtable closures, can be accessed concurrently. This in particular applies to SSL_CTX and SSL_CREDENTIAL objects. Therefore, the mutability annotation has been wrong because access to them would be shared, not exclusive, most of the time. We would prefer the closures to handle the concurrent access and use appropriate locking mechanisms. Signed-off-by: Xiangfei Ding <xfding@google.com> Change-Id: I011fd5808ac7fe6b539be8a5f26cbcf86a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/92087 Reviewed-by: Rudolf Polzer <rpolzer@google.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.
Project links:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: