| commit | 639846e5e47a2aacfd3d368bec1b208af34e68c8 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 09 11:41:18 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Sep 12 21:00:50 2016 +0000 |
| tree | 012674c0c441d5c1080b5918f334821a1448c1d6 | |
| parent | cd2c806530a47d2f4093615be55aa913e0f8b805 [diff] |
Add tests for trailing data in handshake messages. It's easy to forget to check those. Unfortunately, it's also easy to forget to check inner structures, which is going to be harder to stress, but do these to start with. In doing, so fix up and unify some error-handling, and add a missing check when parsing TLS 1.2 CertificateRequest. This was also inspired by the recent IETF posting. Change-Id: I27fe3cd3506258389a75d486036388400f0a33ba Reviewed-on: https://boringssl-review.googlesource.com/10963 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: