The null parameter should be equal to itself In algorithms that do not take parameters beyond the type enum itself, EVP_PKEY_cmp_parameters currently returns -2 to signal some sort of error. But the null parameter is equal to itself, so this should return 1 for equal. This way callers do not need to know ahead of time which algorithms use parameters and which don't, when checking if EVP_PKEYs are of the same algorithm. Update-Note: EVP_PKEY_cmp_parameters for parameter-less algorithms now returns 1 instead of -2. TGP suggests nothing breaks. (This API is not really used outside the library.) Bug: 42290406 Change-Id: Ia467943622094f33c7e6a244c08727a63f7c5a3e Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/87007 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: 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: