Correctly handle max_early_data_size over 2^16 Although we never set a max early data size greater than 2^16, the protocol allows it, so we need to track 32 bits worth of early data written, not 16. (With the size increase, move the field with other 4-byte-aligned values to make better use of struct padding.) The practical impact of this is minor. If a server sent a 0-RTT ticket that allowed > 65K of early data, and if somehow we managed to send that much data before getting the ServerHello, we might exceed the server's limit. The server would then reject the connection. Change-Id: Iee6f562555c062a0b3ded73b98027c3a13609e45 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/95267 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Lily Chen <chlily@google.com> Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.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.
Project links:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: