|author||David Benjamin <firstname.lastname@example.org>||Wed Dec 30 16:51:32 2015 -0500|
|committer||Adam Langley <email@example.com>||Wed Jan 27 21:28:48 2016 +0000|
Remove alert mapping machinery. For TLS, this machinery only exists to swallow no_certificate alerts which only get sent in an SSL 3.0 codepath anyway. It's much less a no-op for SSL 3.0 which, strictly speaking, has only a subset of TLS's alerts. This gets messy around version negotiation because of the complex relationship between enc_method, have_version, and version which all get set at different times. Given that SSL 3.0 is nearly dead and all these alerts are fatal to the connection anyway, this doesn't seem worth carrying around. (It doesn't work very well anyway. An SSLv3-only server may still send a record_overflow alert before version negotiation.) This removes the last place enc_method is accessed prior to version negotiation. Change-Id: I79a704259fca69e4df76bd5a6846c9373f46f5a9 Reviewed-on: https://boringssl-review.googlesource.com/6843 Reviewed-by: Adam Langley <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: