Google Git
Sign in
boringssl / boringssl / 5365f84b9865e40c8db8b530be1206ce8189aac2
commit5365f84b9865e40c8db8b530be1206ce8189aac2[log] [tgz]
authorDavid Benjamin <davidben@google.com>Fri Aug 09 16:52:18 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 14 17:28:20 2024 +0000
tree4aab5037802698ef022b2bda8165290799d134f6
parent41754d58e549d45762f906ba9e0da6ccf28c7b3f [diff]
Remove the now impossible BN_R_NOT_INITIALIZED check in BN_div

This was just checking the bn_correct_top invariant. But since we got
rid of the bn_correct_top invariant and dynamically compute
bn_minimal_width anyway, bn_minimal_width will always be computed such
that the check succeeds.

Bug: 358687140
Change-Id: Idc1abbc46c38d47f319ee5835a5a601a8a3d9c0e
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70171
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
1 file changed
tree: 4aab5037802698ef022b2bda8165290799d134f6
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. gen/
  7. include/
  8. pki/
  9. rust/
  10. ssl/
  11. third_party/
  12. tool/
  13. util/
  14. .bazelignore
  15. .bazelrc
  16. .clang-format
  17. .gitignore
  18. API-CONVENTIONS.md
  19. BREAKING-CHANGES.md
  20. BUILD.bazel
  21. build.json
  22. BUILDING.md
  23. CMakeLists.txt
  24. codereview.settings
  25. CONTRIBUTING.md
  26. FUZZING.md
  27. go.mod
  28. go.sum
  29. INCORPORATING.md
  30. LICENSE
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. PORTING.md
  34. PrivacyInfo.xcprivacy
  35. README.md
  36. SANDBOXING.md
  37. 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: