Google Git
Sign in
boringssl / boringssl.git / b756e68db23aad7376d13ae53290ec53df85efdd
commitb756e68db23aad7376d13ae53290ec53df85efdd[log] [tgz]
authorAdam Langley <agl@chromium.org>Thu Jul 10 09:32:27 2025 -0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 10 09:56:58 2025 -0700
tree76d00bcad6fa66322a270acb881fc5b0316d9eac
parent77f159631b6785fa1e5993fb5c966045e5bcb7a8 [diff]
Keep SHA-1 in crypto.h

85730f21f9 added sha2.h to split out SHA-1. It also updated a number of
files to use sha2.h rather than sha.h. But some external users are
assuming that they get SHA-1 transitively from other headers. Rather
than break them, back off on this on crypto.h. We'll see if x509.h
survives for now.

Change-Id: Iddbb2096c76cd608e3ada0942f87b8b54786d7ca
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80387
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
1 file changed
tree: 76d00bcad6fa66322a270acb881fc5b0316d9eac
  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: