Google Git
Sign in
boringssl / boringssl / 4f76523ffef78ba8650c3d4905c6ff90b82dc303
commit4f76523ffef78ba8650c3d4905c6ff90b82dc303[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Oct 22 11:42:37 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Oct 22 20:54:45 2024 +0000
tree2b8d2e2a655e27a43317b51c4e46b8991092b2a8
parentb90200c8910cb502fa94fa2183c7b02bedc394e4 [diff]
Move tests for libssl's internal utilities into a separate file

ssl_test.cc is getting a bit big. Also these tests broadly won't work in
the shared library build. They happen to all work right now, but only
because all the functions are defined inline in the header. But rather
than having to classify these carefully and rearrange if we ever move it
out of the header, let's just pull them all under a
!BORINGSSL_SHARED_LIBRARY ifdef and don't think about it too hard.

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