Google Git
Sign in
boringssl / boringssl / d0efd8d8478c2707d11add9c45069dc1d6a028a6
commitd0efd8d8478c2707d11add9c45069dc1d6a028a6[log] [tgz]
authorDavid Benjamin <davidben@google.com>Thu Aug 14 18:13:14 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Aug 18 10:17:16 2025 -0700
treeec9297fccd6c926d91b135b2c9dcf3d5867045e8
parenta352ae6bae41c19bf17084f76d37a1b1401c81fc [diff]
More consistently reset EVP_PKEYs in free_it

free_it forgets to reset pkey->ameth and also doesn't reset things if
there's no free function defined (but there's always a free function
defined).

It is almost the case that pkey->ameth gets reset or destroyed
immediately after free_it... except when EVP_PKEY_set_type fails. Fix
that up.

Change-Id: Ib3fe5848fa2ed9cd8723452519b678c4c5ce5ea8
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81307
Reviewed-by: Lily Chen <chlily@google.com>
Commit-Queue: Lily Chen <chlily@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
2 files changed
tree: ec9297fccd6c926d91b135b2c9dcf3d5867045e8
  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: