Google Git
Sign in
boringssl / boringssl / 3544360441f1798981ac2bd4cbdb667f96c2278f
commit3544360441f1798981ac2bd4cbdb667f96c2278f[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Nov 19 17:04:46 2025 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Nov 19 14:29:10 2025 -0800
tree19312d85be49b99929c912651add359d7e0e2f80
parent14e752507fe994581ae59afcf58353b34c45af8d [diff]
Deprecate no-op startup/shutdown ERR functions

Functions like this are usually in the deprecated section. This was
probably early enough that we hadn't actually set this convention.

(This is deprecated in the sense of "don't call this, it's pointless",
not "we actively plan to remove it". To that end, remove the TODO to
remove ERR_load_BIO_strings. Quite a lot more than libjingle calls it,
so I doubt we will ever do away with it.)

Change-Id: Ia13fede6a4b7e25ae37072866acf773c5098989c
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/84387
Reviewed-by: Lily Chen <chlily@google.com>
Commit-Queue: Lily Chen <chlily@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
1 file changed
tree: 19312d85be49b99929c912651add359d7e0e2f80
  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. .clang-format-ignore
  22. .gitignore
  23. API-CONVENTIONS.md
  24. AUTHORS
  25. BREAKING-CHANGES.md
  26. BUILD.bazel
  27. build.json
  28. BUILDING.md
  29. CMakeLists.txt
  30. codereview.settings
  31. CONTRIBUTING.md
  32. FUZZING.md
  33. go.mod
  34. go.sum
  35. INCORPORATING.md
  36. LICENSE
  37. MODULE.bazel
  38. MODULE.bazel.lock
  39. PORTING.md
  40. PRESUBMIT.py
  41. PrivacyInfo.xcprivacy
  42. README.md
  43. SANDBOXING.md
  44. 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: