Google Git
Sign in
boringssl / boringssl / 391bd56eaaa8b0a00cdb0f9a4ed25cc0f11c9791
commit391bd56eaaa8b0a00cdb0f9a4ed25cc0f11c9791[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Nov 18 15:49:12 2024 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Dec 03 22:26:41 2024 +0000
tree798a7d06f1de4ddf27b06f9db631c1e59bbbf28d
parent08a932fe880d336904c52f01df4b140d71d6a5d9 [diff]
Implement receiving KeyUpdates in DTLS 1.3

Receiving KeyUpdates is easy because as soon as you get to the message,
you can act on it. We just needed to fix up some edge cases around epoch
management.

I have included a couple tests which exercise the absolute highest
possible epoch. On my laptop, they take a couple seconds to run each
with an unoptimized shim. That is not very fast, but will maybe be
bearable. But we may need a flag later to disable those tests.

Bug: 42290594
Change-Id: I4276c1ff4547e31ba3367c74606dcf3a2db386f5
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73308
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Nick Harper <nharper@chromium.org>
7 files changed
tree: 798a7d06f1de4ddf27b06f9db631c1e59bbbf28d
  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. .bazelversion
  20. .clang-format
  21. .gitignore
  22. API-CONVENTIONS.md
  23. BREAKING-CHANGES.md
  24. BUILD.bazel
  25. build.json
  26. BUILDING.md
  27. CMakeLists.txt
  28. codereview.settings
  29. CONTRIBUTING.md
  30. FUZZING.md
  31. go.mod
  32. go.sum
  33. INCORPORATING.md
  34. LICENSE
  35. MODULE.bazel
  36. MODULE.bazel.lock
  37. PORTING.md
  38. PrivacyInfo.xcprivacy
  39. README.md
  40. SANDBOXING.md
  41. 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: