| commit | e30fac6371c450833757021d6303d47f66e395f8 | [log] [tgz] |
|---|---|---|
| author | Matthew Braithwaite <mab@google.com> | Thu Apr 05 16:50:21 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat May 05 02:41:04 2018 +0000 |
| tree | 08df48a2f16ada29bfb9f826b4eb9cd10b1ebeb1 | |
| parent | 9fdf7cb97ab760e77b1b35c902f70810c9ae8798 [diff] |
Fuzz SSL_serialize_handoff() and SSL_serialize_handback(). This is done by adding two new tagged data types to the shim's transcript: one for the serialized handoff, and another for the serialized handback. Then, the handshake driver in |TLSFuzzer| is modified to be able to drive a handoff+handback sequence in the same way as was done for testing: by swapping |BIO|s into additional |SSL| objects. (If a particular transcript does not contain a serialized handoff, this is a no-op.) Change-Id: Iab23e4dc27959ffd3d444adc41d40a4274e83653 Reviewed-on: https://boringssl-review.googlesource.com/27204 Commit-Queue: Matt Braithwaite <mab@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Langley <agl@google.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: