Google Git
Sign in
boringssl / boringssl / ca2eba6a5e6a1db7fc970b38c2975fb7bb7153fa
commitca2eba6a5e6a1db7fc970b38c2975fb7bb7153fa[log] [tgz]
authorNick Harper <nharper@chromium.org>Thu Jun 20 22:10:42 2024 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 24 23:02:22 2024 +0000
treeb93b1d99e72a4c6a710258a643934373e5c8d9db
parentf01108e4761e1d4189cb134322c3cb01dc71ef87 [diff]
[DTLS] Use absolute instead of relative epoch numbers.

DTLS 1.3 needs to be able to handle absolute epoch numbers (e.g. "write
data at the handshake epoch" instead of "write data at the current
epoch").

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

There are other files in this directory which might be helpful: