Google Git
Sign in
boringssl / boringssl / 73c4a5d0b5f78dabaa29e5e9f2844e1bf4e16bdf
commit73c4a5d0b5f78dabaa29e5e9f2844e1bf4e16bdf[log] [tgz]
authorMatt Mueller <mattm@google.com>Fri Dec 08 18:37:42 2023 -0800
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Dec 11 18:53:49 2023 +0000
treedf26a0de8466c070d9a79e564d828864cc4640ac
parent811de7adb2b1742fe10ebcaf3b8dda66301c3cc1 [diff]
Call CheckPathAfterVerification in deadline/iteration limit case

For symmetry with the CheckPathAfterVerification calls that happen
when partial paths are found during pathbuilding.

Also removes the DebugLog after VerifyCertificateChain, as the
CheckPathAfterVerification is already called there, the delegate can
do any logging it wants there.

Bug: chromium:634484
Change-Id: I93e472b6ec813536b1808f1459a3a477b1b0c876
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/64667
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: Matt Mueller <mattm@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: Matt Mueller <mattm@google.com>
3 files changed
tree: df26a0de8466c070d9a79e564d828864cc4640ac
  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: