|tagger||Adam Langley <email@example.com>||Thu Jun 15 12:10:35 2017 -0700|
|author||David Benjamin <firstname.lastname@example.org>||Wed Jun 14 18:45:29 2017 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Jun 15 16:18:42 2017 +0000|
Add a test for invalid alert types. This doesn't hugely matter, but I noticed it was some missing coverage. Change-Id: I3e425d47fbbeaacd9da2ae883f34e89b4562ec11 Reviewed-on: https://boringssl-review.googlesource.com/17184 Commit-Queue: Steven Valdez <email@example.com> Reviewed-by: Steven Valdez <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: