Mark x509v3_cache_extensions as const While it does mutate the X509 object, it is thread-safe and logically const. When we fix this to instead fill in cached fields on parse, this will be more obviously const-correct. In the meantime, mark this as const so it doesn't get in the way of keeping other fields const. Bug: 443261873 Change-Id: Id1a819f0342d468f3e904cc97a7df9b009090482 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/103855 Reviewed-by: Xiangfei Ding <xfding@google.com> Commit-Queue: David Benjamin <davidben@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: