Google Git
Sign in
boringssl / boringssl / 52ef94f532b5f98d284943f83dc4d3392c198c28
commit52ef94f532b5f98d284943f83dc4d3392c198c28[log] [tgz]
authorDavid Benjamin <davidben@google.com>Thu May 01 10:43:26 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 02 10:01:24 2025 -0700
tree8ed2b4ebd221592ffab8df34e9022c3a2626b634
parent35e07a80d8c8b35c390467f485a9be4202ed9ec1 [diff]
Clean up ssl_file.cc

- Use scopers

- BIO_new + BIO_read_filename can be replaced with BIO_new_file (note
  BIO_read_filename is "rb", not "r", on Windows)

- SSL_CTX_use_certificate_chain_file is more straightforward if we use
  SSL_CTX_add1_chain_cert. add0 doesn't even save a refcount bump
  because we internally transform it into a CRYPTO_BUFFER anyway.

Bug: 394340436
Change-Id: I586214b6547d5d85e589242eb218d296223778c9
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79010
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
1 file changed
tree: 8ed2b4ebd221592ffab8df34e9022c3a2626b634
  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: