Google Git
Sign in
boringssl / boringssl / 69be68ca92936dd8ddb9e7bf1a491bb89f2f1a8f
commit69be68ca92936dd8ddb9e7bf1a491bb89f2f1a8f[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Oct 16 15:52:09 2024 -0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Oct 23 22:24:57 2024 +0000
treebb5d61ae9ad2bca9eb2be6a72629f0cceea47e78
parent453207b73e9997cd49f79fee98843255638e74a4 [diff]
Pull the DTLS reassembly bitmap into its own abstraction

We'll use the same bitmap for tracking which parts of a message have
been ACKed. To that end, I've gone ahead and implemented a
NextUnmarkedRange.

This does make the hm_fragment structure a little larger, but we
indirect them to the heap, so I think this is fine. In the steady state,
they do not contribute to per-connection memory use.

Bug: 42290594
Change-Id: I326520454ee4d6832248b50ea3f5205f41d74cbe
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72269
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Nick Harper <nharper@chromium.org>
Commit-Queue: David Benjamin <davidben@google.com>
3 files changed
tree: bb5d61ae9ad2bca9eb2be6a72629f0cceea47e78
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. infra/
  11. pki/
  12. rust/
  13. ssl/
  14. third_party/
  15. tool/
  16. util/
  17. .bazelignore
  18. .bazelrc
  19. .clang-format
  20. .gitignore
  21. API-CONVENTIONS.md
  22. BREAKING-CHANGES.md
  23. BUILD.bazel
  24. build.json
  25. BUILDING.md
  26. CMakeLists.txt
  27. codereview.settings
  28. CONTRIBUTING.md
  29. FUZZING.md
  30. go.mod
  31. go.sum
  32. INCORPORATING.md
  33. LICENSE
  34. MODULE.bazel
  35. MODULE.bazel.lock
  36. PORTING.md
  37. PrivacyInfo.xcprivacy
  38. README.md
  39. SANDBOXING.md
  40. STYLE.md
README.md

BoringSSL

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: