| commit | 6254482b9dcf85f183f00602932ddd06c8ed556b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <[email protected]> | Mon Nov 04 16:47:46 2024 +0000 |
| committer | Boringssl LUCI CQ <[email protected]> | Fri Nov 15 20:32:50 2024 +0000 |
| tree | 3bcdf5dbb79e04f7c4babe420d1290cefc3cbe8e | |
| parent | a5d14bed7004ee86c9905314999f81b50064999d [diff] |
runner: Rearrange 0-RTT code in server slightly The point at which we flush is tricky for testing DTLS 1.3 ACKs. This rearrangement is not sufficient to make that work, but I wanted to pull this into a separately reviewable CL first. The changes are: - We can derive keys and set the out keys very early - I've removed the shouldSkipEarlyData() check. That check is unnecessary because we're already checking for whether the server accepted early data in EncryptedExtensions. (Also it doesn't make sense to apply that check to reading a bit of early data, but not to reading EndOfEarlyData. The conditions on those should match.) Change-Id: Ie1909bb5f8a8a2aeab05ba0f95155ce45eb160f3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72948 Reviewed-by: Nick Harper <[email protected]> Commit-Queue: David Benjamin <[email protected]>
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: