|author||David Benjamin <firstname.lastname@example.org>||Mon Sep 21 13:55:16 2020 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Sep 21 18:28:28 2020 +0000|
Add SSL_CIPHER_get_protocol_id. This was introduced in OpenSSL 1.1.1, and wpa_supplicant expects us to have it. We had this same function as SSL_CIPHER_get_value (to match SSL_get_cipher_by_value). Align with upstream's name. It seems we also had a ssl_cipher_get_value lying around, so fold them together. (I've retained the assert in ssl_cipher_get_value as it seems reasonable enough; casting a hypothetical SSLv2 cipher ID to uint16_t would not behave correctly.) Change-Id: Ifbec460435bbc483f2c3de988522e321f2708172 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42966 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: