|author||David Benjamin <firstname.lastname@example.org>||Thu Oct 12 19:11:47 2017 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Oct 17 21:28:51 2017 +0000|
Make all read errors idempotent. Now that we've gotten everything, test this by just making bssl_shim run all errors twice. The manual tests added to ssl_test.cc may now be removed. Bug: 206 Change-Id: Iefa0eae83ba59b476e6b6c6f0f921d5d1b72cbfb Reviewed-on: https://boringssl-review.googlesource.com/21886 Commit-Queue: Steven Valdez <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.com> Reviewed-by: Steven Valdez <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: