|author||David Benjamin <email@example.com>||Mon May 20 18:25:56 2019 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Tue May 21 17:08:43 2019 +0000|
Align PKCS12_parse closer to OpenSSL. OpenSSL uses the private key to find the leaf certificate. cryptography.io's tests rely on this. Update-Note: PKCS12_parse's behavior changes slightly. Affected callers are recommended to switch to PKCS12_get_key_and_certs, which has much more predictable behavior and has no pressures from 3rd-party software to match OpenSSL's quirks. Change-Id: I4ee2befbd56a0882ee166f00e748f2fe58ac6a86 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36125 Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: 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: