Google Git
Sign in
boringssl / boringssl / 94d7b7e4f2c355858e3d3943ffe33d26af3e5fa5
commit94d7b7e4f2c355858e3d3943ffe33d26af3e5fa5[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Oct 08 16:15:50 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Oct 23 13:34:11 2025 -0700
tree89edec35c17125d91386167fcbfe79a55c352fb2
parentb3d8b40a3612f0a2c3ba40c56a7e49d238cd9c23 [diff]
Fold p_${alg}_asn1.cc into p_${alg}.cc

The two method tables both need access to the same internal EVP_PKEY
representation. For the old algorithms, those representations were
one-to-one with the low-level types, Ed25519 and X25519 ended up
defining custom things.

Folding the files together lets us limit it to one translation unit that
handles the EVP binding for that algorithm.

Change-Id: I3b55f543047f2b0af4a3759446f2ff10487f1712
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82988
Reviewed-by: Lily Chen <chlily@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
19 files changed
tree: 89edec35c17125d91386167fcbfe79a55c352fb2
  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. PRESUBMIT.py
  40. PrivacyInfo.xcprivacy
  41. README.md
  42. SANDBOXING.md
  43. 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: