|author||Matthew Braithwaite <email@example.com>||Mon Jan 13 15:45:33 2020 -0800|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Wed Jan 15 20:38:44 2020 +0000|
test_state.cc: serialize the test clock. This is needed for some TLS 1.3 split-handshake tests. Because TestState::Deserialize doesn't check for CBS_len() == 0, it should be a compatible change to tack additional data onto the end of the serialized test state. Change-Id: I16464b6e27ab2e9afd0d505719095b4895e652a4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39546 Commit-Queue: Matt Braithwaite <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: