| commit | 0eb01c2780b81970d699fe2ca3533f31a3d90ce9 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Oct 22 17:16:34 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 25 21:54:16 2024 +0000 |
| tree | 06f2a5afc16d0cddfcc05d54d002c1e60ee6ca1d | |
| parent | ddc432876c33e076d5945f56d31ff8a4c250b6f3 [diff] |
Implement a fixed-width ring buffer for DTLS 1.3 DTLS 1.3 ACK management requires that we track: - Received record numbers, to send in ACKs - Information about unacked outgoing records, so we can update message state when ACKs from in Both of those lists can, in principle, grow unboundedly, but can also be freely dropped. This class is intended as a fixed-width ring buffer for managing this. I was worried I'd need need to dip into the scary uninitialized functions again but actually this is just an InplaceVector and an integer, so that was quite satisfying. Bug: 374890768 Change-Id: I4037ef5875a2df70f0dc16df1bbba478362cecce Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72274 Reviewed-by: Nick Harper <nharper@chromium.org> Commit-Queue: David Benjamin <davidben@google.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: