| commit | 517b06eb997d7080ff2261fafdfbc43af0f2f709 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Nov 02 09:36:25 2024 +0000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 14 15:39:05 2024 +0000 |
| tree | d0043f24bdb7ea3ca720f4cafef39dd8c09cc24e | |
| parent | 61725eafad52eab7063cca7ae3ca763d2b147583 [diff] |
Send one ACK immediately after the handshake in DTLS 1.3 servers This does not yet implement sending ACKs in general, just the one immediate ACK when the handshake completes. The general case will require scheduling an ACK-send timer, but this one can be sent immediately. One interesting case to test is when the server would like to ACK Finished, but cannot because the records were merged with fragments that we had to discard. Bug: 42290594 Change-Id: I64b3f8ecbef4ffee68d923f83ea89d2349847f8b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72867 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Nick Harper <nharper@chromium.org>
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: