Google Git
Sign in
boringssl / boringssl / bf4cf6938a77f1aca83ef529dce96681efd1e6c5
commitbf4cf6938a77f1aca83ef529dce96681efd1e6c5[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Dec 17 10:52:31 2024 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jan 13 13:44:48 2025 -0800
treebfba9ad022682c54055186c002910251970a98f4
parente822de3aeb51d7c2ab17bea73ab3306b95254209 [diff]
Start using bssl::UniquePtr in libcrypto

No types with destructors or anything yet, but let's start getting rid
of the 'goto err's everywhere. I've opportunistically replaced NULL with
nullptr while I'm here, though we should probably just replace that en
masse in the library since even libssl is still a mix.

(For some reason I thought unique_ptr != NULL didn't work because NULL
was the zero literal, but actually unique_ptr != 0 works just fine.)

Change-Id: I8d749b2ef42cc76e0a66a25033ce880be80d2693
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/75227
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: Bob Beck <bbe@google.com>
5 files changed
tree: bfba9ad022682c54055186c002910251970a98f4
  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: