Google Git
Sign in
boringssl / boringssl / 9d479673ccd027eaee60e4c382ed4a463d471a96
commit9d479673ccd027eaee60e4c382ed4a463d471a96[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Nov 20 23:53:04 2023 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Nov 29 22:36:53 2023 +0000
tree8bbbb1807edf5a49a663ae03bf524c2e003e31ab
parent790f96bdb549d4dd81a88f0a1fd2fe466b712d97 [diff]
Simplify X509_VERIFY_PARAM_new and X509_VERIFY_PARAM_free

Although new and free share a zero function, most of the function is
irrelevant to both (either because we're about to free the object or
have allocated it with zalloc), or only one of them.

While I'm here, remove some unnecessary NULL checks guarding free
functions.

Change-Id: I9906ebc16c931f51b6341958bcf0a10426a1211b
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/64136
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
1 file changed
tree: 8bbbb1807edf5a49a663ae03bf524c2e003e31ab
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. include/
  7. pki/
  8. rust/
  9. ssl/
  10. third_party/
  11. tool/
  12. util/
  13. .clang-format
  14. .gitignore
  15. API-CONVENTIONS.md
  16. BREAKING-CHANGES.md
  17. BUILDING.md
  18. CMakeLists.txt
  19. codereview.settings
  20. CONTRIBUTING.md
  21. FUZZING.md
  22. go.mod
  23. go.sum
  24. INCORPORATING.md
  25. LICENSE
  26. PORTING.md
  27. README.md
  28. SANDBOXING.md
  29. sources.cmake
  30. 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:

There are other files in this directory which might be helpful: