Google Git
Sign in
boringssl / boringssl / 30742686c6958159ab392129a51d57e1ba1f67a2
commit30742686c6958159ab392129a51d57e1ba1f67a2[log] [tgz]
authorDavid Benjamin <davidben@google.com>Thu Jan 11 13:36:30 2024 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jan 11 19:14:19 2024 +0000
tree6734c73d0f51b7df152a2df2f5cfb82bd1a6a44f
parent0c8bc4653e34892dc291b48fb38e180ce92b5921 [diff]
Fix PKI test data list in sources.cmake

This reflects
https://boringssl-review.googlesource.com/c/boringssl/+/64688. I really
need to rework the build so that we notice mistakes in this list.

Change-Id: I9c64361cbcdb9a205ddccb97df5c286e7ce834fe
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65247
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Bob Beck <bbe@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
1 file changed
tree: 6734c73d0f51b7df152a2df2f5cfb82bd1a6a44f
  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: