Google Git
Sign in
boringssl / boringssl / 9588d3c35d43f3bb27f4fa8dff8e65bf6b84d2a5
commit9588d3c35d43f3bb27f4fa8dff8e65bf6b84d2a5[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Oct 22 15:35:10 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Oct 25 18:01:29 2024 +0000
treed062f5de4a911365e99f551a3344b73fb9cf08ec
parent7628194c2305548364d971406406e06e1153dd31 [diff]
Use DTLSRecordNumber in DTLSWriteEpoch

This saves 8 bytes per write epoch and is a bit tidier. We could do
something similar with DTLSReadEpoch if we hid it in DTLSReplayBitmap
but that was a bit messy.

Bug: 42290594
Change-Id: I3de19ef90d59566c303bf3b2ff85e76bafc790d4
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72272
Reviewed-by: Nick Harper <nharper@chromium.org>
Commit-Queue: David Benjamin <davidben@google.com>
7 files changed
tree: d062f5de4a911365e99f551a3344b73fb9cf08ec
  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: