Google Git
Sign in
boringssl / boringssl / 33a5e94645787d74593efa0e63200a31372325a2
commit33a5e94645787d74593efa0e63200a31372325a2[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Nov 22 02:55:41 2023 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Dec 05 16:31:07 2023 +0000
tree415756727061068ed282a67bc8652fc6509f9b45
parent51ae958ff7c99103932e07905c40cbc71a22b389 [diff]
Fix the names of some X509_STORE_CTX functions

This matches an upstream change. Add macros for the old names. We may be
able to unexport these, but for now just pick up the less confusing
names.

(I found only one user of one of them, goma, which will be replaced next
year. Though wanting *some* API to query the dirhash machinery is not
completely implausible.)

Change-Id: Idd2352c07c294c4f63c4ef12e5d97804f42225b9
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/64254
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
3 files changed
tree: 415756727061068ed282a67bc8652fc6509f9b45
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. include/
  7. pki/
  8. rust/
  9. ssl/
  10. third_party/
  11. tool/
  12. util/
  13. .clang-format
  14. .gitignore
  15. API-CONVENTIONS.md
  16. BREAKING-CHANGES.md
  17. BUILDING.md
  18. CMakeLists.txt
  19. codereview.settings
  20. CONTRIBUTING.md
  21. FUZZING.md
  22. go.mod
  23. go.sum
  24. INCORPORATING.md
  25. LICENSE
  26. PORTING.md
  27. README.md
  28. SANDBOXING.md
  29. sources.cmake
  30. 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:

There are other files in this directory which might be helpful: