Google Git
Sign in
boringssl / boringssl / 5bdf5e4ac251e7e9eca5693104d802d94a28f28b
commit5bdf5e4ac251e7e9eca5693104d802d94a28f28b[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Feb 01 14:06:29 2023 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Feb 02 23:07:22 2023 +0000
treeb1925b792bcbbe3c384da72193255c84b8b37be6
parent3c7053975b35a631f477f42f07502003d35aa2ff [diff]
Silence an uninitialized variable false positive in GCC.

When building with OPENSSL_NO_ASM, things are inlined enough that GCC
figures out bn_reduce_once reads words, but not that
bn_big_endian_to_words initializes the parts that are read.

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