| commit | ddc432876c33e076d5945f56d31ff8a4c250b6f3 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Oct 22 16:12:52 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 25 19:11:05 2024 +0000 |
| tree | 974f35d057947cd6fcfdab035c10fcb607e0f6d2 | |
| parent | bf1fe798d0e3d933aed07efa98796c2702ccf450 [diff] |
Amortize invariant maintenance in DTLSMessageBitmap After we receive a handshake fragment, we check if the fragment is now complete. This requires scanning over the entire message bitmap. This is the one step in MarkRange that does not scale with the number of bytes the peer sent us. This is not really a DoS vector due to message size limits but, in principle, the peer could send us all but the last byte of a message and then repeatedly send us the first byte, causing us to scan over msg_len / 8 bytes each time. We can easily amortize this by saving how far we scanned last time, because bits will never be unmarked. This means we only advance over each byte in the bitmap once. Change-Id: I802003d587de4c0a45650b891c76cea8b10acd17 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72287 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: