Add definition of OSSL_PARAM OSSL_PARAM was previously not defined and was expected to be null when passed as function parameters. Since some consumers need it to compile, for compatibility with OpenSSL, this CL defines the struct and adds the macro for a terminating OSSL_PARAM. BoringSSL functions still expect an OSSL_PARAM array argument to either be null or start with a terminaing OSSL_PARAM. Bug: 497718229 Change-Id: I6c42cf488d8f2aefc6dd69c4b2b994c86a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/91887 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: 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: