Google Git
Sign in
boringssl / boringssl / f6bf5e2cc110b2b2ac62c0d900c7dafca89c376c
commitf6bf5e2cc110b2b2ac62c0d900c7dafca89c376c[log] [tgz]
authorDavid Benjamin <davidben@google.com>Sat Mar 22 12:37:10 2025 +0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Mar 25 10:50:32 2025 -0700
tree521cecbe204960ad3b78b276edd6f6ccda47aa17
parent02f0d8776ecd83a1c663db2eaba6283aa72cc5b8 [diff]
Add APIs to access DTLS record layer state

DTLS record layer state is more complex and, with DTLS 1.3, we could not
make the simplifying assumptions that we did in DTLS 1.2. Expose enough
information so that, at idle points, we can extract state. See
go/dtls13-handover (internal) for details.

This requires maintaining some extra state on each epoch. We could
recover most of it if we did a better job not allocating unused fields
in DTLS by reworking the transport-specific portions.

Update-Note: Callers that need DTLS record layer state should migrate to
the new APIs. For now, the old APIs continue to work for DTLS 1.2, but
once caller have migrated, we'll make them TLS-only.

Bug: 42290608
Change-Id: Id3f7185e9715b9ee0e5e68108fd44d9484abd569
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77967
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
6 files changed
tree: 521cecbe204960ad3b78b276edd6f6ccda47aa17
  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. AUTHORS
  24. BREAKING-CHANGES.md
  25. BUILD.bazel
  26. build.json
  27. BUILDING.md
  28. CMakeLists.txt
  29. codereview.settings
  30. CONTRIBUTING.md
  31. FUZZING.md
  32. go.mod
  33. go.sum
  34. INCORPORATING.md
  35. LICENSE
  36. MODULE.bazel
  37. MODULE.bazel.lock
  38. PORTING.md
  39. PrivacyInfo.xcprivacy
  40. README.md
  41. SANDBOXING.md
  42. 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: