Google Git
Sign in
boringssl / boringssl.git / ea52bc3f7558ff13f29a478be614b31c87b27c52
commitea52bc3f7558ff13f29a478be614b31c87b27c52[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Feb 10 13:48:18 2026 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Feb 10 12:28:50 2026 -0800
treef17866b6f7518af254cbf93c4deb08615a2b5a06
parent73cd946964c555a39730592db4b540accbafac6c [diff]
evp_test: Fix MaybeReplaceWithCopy for EVP_MD_CTX

The corresponding EVP_PKEY_CTX pointer wasn't being updated. We actually
don't have an API to access the copied object, but OpenSSL 1.1.x added
EVP_MD_CTX_pkey_ctx, which seems fine enough.

I think this happened to work because none of the EVP_MD_CTX-based tests
set anything on the EVP_PKEY_CTX.

OpenSSL 3.x renamed it to EVP_MD_CTX_get_pkey_ctx, along with a host of
other such getters. I've stuck with the 1.1.x name for now, since we're
mostly not targetting the 3.x API yet.

Change-Id: Iefb325ae40beca843de5a03508d072119a9974ea
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/89127
Reviewed-by: Lily Chen <chlily@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
4 files changed
tree: f17866b6f7518af254cbf93c4deb08615a2b5a06
  1. .bcr/
  2. .github/
  3. bench/
  4. cmake/
  5. crypto/
  6. decrepit/
  7. docs/
  8. fuzz/
  9. gen/
  10. include/
  11. infra/
  12. pki/
  13. rust/
  14. ssl/
  15. third_party/
  16. tool/
  17. util/
  18. .bazelignore
  19. .bazelrc
  20. .bazelversion
  21. .clang-format
  22. .clang-format-ignore
  23. .gitignore
  24. API-CONVENTIONS.md
  25. AUTHORS
  26. BREAKING-CHANGES.md
  27. BUILD.bazel
  28. build.json
  29. BUILDING.md
  30. CMakeLists.txt
  31. codereview.settings
  32. CONTRIBUTING.md
  33. FUZZING.md
  34. go.mod
  35. go.sum
  36. INCORPORATING.md
  37. LICENSE
  38. MODULE.bazel
  39. MODULE.bazel.lock
  40. PORTING.md
  41. PRESUBMIT.py
  42. PrivacyInfo.xcprivacy
  43. README.md
  44. SANDBOXING.md
  45. SECURITY.md
  46. 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: