Google Git
Sign in
boringssl / boringssl / 0317d633c0a05dfd0bbafc1a341032798145f1c9
commit0317d633c0a05dfd0bbafc1a341032798145f1c9[log] [tgz]
authorNick Harper <nharper@chromium.org>Thu Oct 24 00:26:12 2024 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Oct 24 21:04:41 2024 +0000
tree39d211262a6ebddd0988e63d8da895eabf59c73b
parent52d5e1b6d3f0669868f0ba95792b527907a67fdd [diff]
Resolve DTLS 1.3 TODOs in ssl_test.cc.

Now that resumption is supported in DTLS 1.3, the NewSessionTicket TODOs
for DTLS 1.3 in ssl_test.cc can be removed and tests enabled.

Bug: 42290594
Change-Id: I74986a2f14b8ea5b8988793a52f0ae308bb730c2
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72408
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Nick Harper <nharper@chromium.org>
Auto-Submit: Nick Harper <nharper@chromium.org>
Reviewed-by: David Benjamin <davidben@google.com>
1 file changed
tree: 39d211262a6ebddd0988e63d8da895eabf59c73b
  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: