|author||Alessandro Ghedini <firstname.lastname@example.org>||Wed Sep 28 21:04:25 2016 +0100|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Fri Sep 30 00:45:19 2016 +0000|
Implement SSL_CTX_set1_curves_list() This function is used by NGINX to enable specific curves for ECDH from a configuration file. However when building with BoringSSL, since it's not implmeneted, it falls back to using EC_KEY_new_by_curve_name() wich doesn't support X25519. Change-Id: I533df4ef302592c1a9f9fc8880bd85f796ce0ef3 Reviewed-on: https://boringssl-review.googlesource.com/11382 Reviewed-by: David Benjamin <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: