Google Git
Sign in
boringssl / boringssl.git / a200650ac344338f9af86822266984804eb86370
commita200650ac344338f9af86822266984804eb86370[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Mar 18 18:18:57 2024 +1000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Mar 20 06:17:42 2024 +0000
tree738f52ed1e024b1adbfe991291541348f33b05a6
parent31442d490cc487998e0fb351e854a9ff9b3ac35e [diff]
Trim unused files from PKI_TEST_DATA

The Python scripts (which probably don't work anymore) don't need to be
shipped to the test. Neither to the .h files. Also we have some random
files that are remnants of being around Chromium.

We also don't need the ship the .key files.

Change-Id: I847b449accee1c4005304380b47f3ff876a09fa5
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/67291
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
4 files changed
tree: 738f52ed1e024b1adbfe991291541348f33b05a6
  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: