Google Git
Sign in
boringssl / boringssl / 07a1e6236ee89238b4b70af306211fbe5d063f9c
commit07a1e6236ee89238b4b70af306211fbe5d063f9c[log] [tgz]
authorDavid Benjamin <davidben@google.com>Fri Apr 18 14:29:42 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 18 11:46:16 2025 -0700
treed7d1e3fb78f158a3f0b6d467d0acdb212a99f864
parent999dd48f4d6c52b7c79253c76cd0160591a2c25b [diff]
Fix v2i_AUTHORITY_INFO_ACCESS

Regressed in
https://boringssl-review.googlesource.com/c/boringssl/+/78687 because I
forgot to account for the use-after-move (clang-tidy would sure be
nice). Fix by just waiting for the object to be finished before adding
it to the stack, which is tidier anyway.

Looked through that CL and previous scoper CLs and I think this is the
only instance.

Fixed: 411460548
Change-Id: Ib1ad77127dc1bd611ea971188c4cb078547b596f
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78727
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
2 files changed
tree: d7d1e3fb78f158a3f0b6d467d0acdb212a99f864
  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: