7a55c80271
This originally didn't work because we installed an async BIO, while QUIC uses the BIO to mock out a QUIC transport. Our QUIC IO callbacks don't have a meaningful notion of sync vs async, so no-op this portion of the -async flag. The immediate motivation is I'd like to make addExtensionTests run over all protocols, and having the async tests fail is inconvenient. However, async tests in QUIC is still meaningful anyway to support various callbacks, so I've removed the workaround in the state machine coverage tests. (Though most of those async tests are redundant as they're concerned with IO, not callbacks.) Along the way, the various handshake record controls are irrelevant to QUIC, so this actually results in a net decrease in redundant tests. Change-Id: I67c1ee48cb2d85b47ae3328fecfac86a24aa2ed1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/44987 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com>
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.
Project links:
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.
- BREAKING-CHANGES.md: notes on potentially-breaking changes.
- SANDBOXING.md: notes on using BoringSSL in a sandboxed environment.