| commit | 42e3e191e41d547f2850076fa709f079de5c536c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jan 27 10:06:07 2017 -0500 |
| committer | Adam Langley <agl@google.com> | Fri Jan 27 16:24:19 2017 +0000 |
| tree | 212138682046fff917edf490217f4cc0fd994787 | |
| parent | 830f7009ebd606c0b10fe8bd16bde6256eeecec5 [diff] |
Restore mapping BIO_flush errors to -1. This was originally changed so that flush_flight could forward BIO_write errors as-is, but we can and probably should still map BIO_flush errors. This is unlikely to matter (every relevant BIO likely just has a no-op flush which returns one), but, e.g., our file BIO returns 0, not -1, on error. We possibly should also be mapping BIO_write errors, but I'll leave that alone for now. It's primarily BIO_read where the BIO return value must be preserved due to error vs. EOF. (We probably can just remove the BIO_flush calls altogether, but since the buffer BIO forwarded the flush signal it would be a user-visible behavior change to confirm.) Change-Id: Ib495cc5d043867cf964f99b7ee4535114f7b2230 Reviewed-on: https://boringssl-review.googlesource.com/13367 Commit-Queue: David Benjamin <davidben@google.com> 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: