Google Git
Sign in
boringssl / boringssl / fda22fa7dbe9b841a2605ca78fbd32f2e3cb1a91
commitfda22fa7dbe9b841a2605ca78fbd32f2e3cb1a91[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Apr 08 17:35:44 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 14 13:22:39 2025 -0700
treed9765a51c8c6c0e2603d4e4dede19d39dcbe9d6b
parenta795743127c0efc250457492f5362f72fe0acb97 [diff]
Add some CBB-based functions for crypto/x509 and crypto/asn1 types

For now, they forward to the i2d/i2c functions instead of being
CBB-based themselves. I've added a tag parameter to the crypto/asn1 ones
in anticipation of them being used for implicit tagging, once the rest
of the legacy parser becomes CBB-based.

But we already have enough things that cross the line that this seems
worthwhile.

Bug: 42290417
Change-Id: Ide588fe04d3d5862ca003ab94b068c009eadf2b1
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78448
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
8 files changed
tree: d9765a51c8c6c0e2603d4e4dede19d39dcbe9d6b
  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: