|author||Adam Langley <firstname.lastname@example.org>||Mon Feb 26 13:51:55 2018 -0800|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Feb 27 20:13:53 2018 +0000|
Update dummy PQ extension for round two. In this round, Google servers will echo the extension in order to test the latency of both parties sending a PQ key-agreement message. The extension is sent (and echoed) for both full and resumption handshakes. This is intended to mirror the overhead of TLS 1.3 (even when using TLS 1.2), as a resumption in TLS 1.3 still does a fresh key agreement. Change-Id: I9ad163afac4fd1d916f9c7359ec32994e283abeb Reviewed-on: https://boringssl-review.googlesource.com/26185 Commit-Queue: David Benjamin <email@example.com> Reviewed-by: 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: