c7df7967fa
Chaining doesn't make much sense. This means we have a discontinuity when buffer BIOs are empty. For a general filter BIO, this isn't even meaningful. E.g., the base64 BIO's next_bio doesn't use the same units (There's one consumer which does call BIO_pending on a base64 BIO, hits this case, and is only working on accident, I've left it alone for this CL until we can fix that consumer.) The DTLS code, notably, assumes BIO_wpending to only report what's in the buffer BIO. Ideally we'd get rid of the buffer BIO (I'll work on this next), but, in the meantime, get the sizing right. The immediate motivation is ssl_test using a BIO pair for DTLS doesn't work. We've just been lucky none of the tests have been near the MTU. The buffer BIO is actually unused outside of the SSL stack, so this shouldn't break external consumers. But for the base64 BIO consumer mentioned above, I see nothing else which relies on this BIO_[w]pending chaining. Change-Id: I6764df8ede0f89fe73c774a8f7c9ae4c054d4184 Reviewed-on: https://boringssl-review.googlesource.com/12964 Reviewed-by: Adam Langley <agl@google.com> |
||
|---|---|---|
| .github | ||
| crypto | ||
| decrepit | ||
| fuzz | ||
| include/openssl | ||
| infra/config | ||
| ssl | ||
| third_party/android-cmake | ||
| tool | ||
| util | ||
| .clang-format | ||
| .gitignore | ||
| API-CONVENTIONS.md | ||
| BUILDING.md | ||
| CMakeLists.txt | ||
| codereview.settings | ||
| CONTRIBUTING.md | ||
| FUZZING.md | ||
| INCORPORATING.md | ||
| LICENSE | ||
| PORTING.md | ||
| README.md | ||
| STYLE.md | ||
BoringSSL
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:
- PORTING.md: how to port OpenSSL-using code to BoringSSL.
- BUILDING.md: how to build BoringSSL
- INCORPORATING.md: how to incorporate BoringSSL into a project.
- API-CONVENTIONS.md: general API conventions for BoringSSL consumers and developers.
- STYLE.md: rules and guidelines for coding style.
- include/openssl: public headers with API documentation in comments. Also available online.
- FUZZING.md: information about fuzzing BoringSSL.
- CONTRIBUTING.md: how to contribute to BoringSSL.