Google Git
Sign in
boringssl / boringssl / f83f98788b63d7b50e5c9a26fe5b97d0dd82ac8c
commitf83f98788b63d7b50e5c9a26fe5b97d0dd82ac8c[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Apr 28 17:18:38 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 29 11:51:38 2025 -0700
tree3d681b8b9269d6d48d2fd577917a0e6fa3964332
parent6be2f31b1381e094d4f806787fc0b08e6c82c678 [diff]
Remove STACK_OF(BIGNUM) from BN_CTX

With C++, we have better tools for containers than STACK_OF(T). We can
also just declare constructors and destructors for our types.

This also fixes a FIPS + CFI incompatibility. STACK_OF(BIGNUM), as part
of the mess type erasure tricks it used, needed to pass a function
pointer taken from BCM, out of BCM. (This doesn't fix all the issues.
There are still two more.)

It would really be nice to take BN_CTX out of BCM altogether, but that
will take a lot more work. Either way, it can be the first guinea pig
for a destructor-managed libcrypto type.

Update-Note: With something in libcrypto using crypto/mem_internal.h, we
now depend on quite a bit more of an STL in libcrypto. But we already
depended on <memory> for std::unique_ptr before.

Bug: 394340436, 413519751
Change-Id: Ia26ea9cd6b01542d569d6ef6f41f528b3cc72c14
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78890
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
1 file changed
tree: 3d681b8b9269d6d48d2fd577917a0e6fa3964332
  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: