|author||Adam Langley <firstname.lastname@example.org>||Fri Jul 19 15:18:33 2019 -0700|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Fri Jul 19 23:11:44 2019 +0000|
Move the PQ-experiment signal to SSL_CTX. In the case where I need it, it's easier for it to be on the context rather than on each connection. Change-Id: I5da2929ae6825d6b3151ccabb813cb8ad16416a1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36746 Commit-Queue: Adam Langley <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: David Benjamin <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: