Google Git
Sign in
boringssl / boringssl / c28dcd61c9db318850ddec747b41a78745d8f45a
commitc28dcd61c9db318850ddec747b41a78745d8f45a[log] [tgz]
authorNick Harper <nharper@chromium.org>Wed Oct 23 23:17:32 2024 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Oct 24 01:58:11 2024 +0000
tree41a89ef003f1b566adea4f3301d52894805de635
parent69be68ca92936dd8ddb9e7bf1a491bb89f2f1a8f [diff]
Rename DTLS 1.3 TODOs.

Prior to the buganizer migration, the DTLS 1.3 tracking bug was
crbug.com/boringssl/715. To make it easier to find all TODOs for the
DTLS 1.3 work, this changes them to point to the same bug under the new
number.

Change-Id: I585c551947ded2b82e3e1faaf133a518961686ea
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72407
Reviewed-by: David Benjamin <davidben@google.com>
Auto-Submit: Nick Harper <nharper@chromium.org>
Commit-Queue: David Benjamin <davidben@google.com>
3 files changed
tree: 41a89ef003f1b566adea4f3301d52894805de635
  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: