Google Git
Sign in
boringssl / boringssl / bddc709c63adb7877296b42c7f3edeb2ad6b7564
commitbddc709c63adb7877296b42c7f3edeb2ad6b7564[log] [tgz]
authorAdam Langley <agl@chromium.org>Thu Aug 15 10:12:07 2024 -0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Aug 15 17:56:44 2024 +0000
tree371c9d90c1177ab909603d1d8912c0e6d9595728
parent1a87f285b5898ab63f54ea7e9a4e521a22078032 [diff]
Correct DOS line endings.

These files were derived from CAVP, which used DOS line endings. Several
environments will automatically convert line endings and this leads to a
mismatch if strictly comparing against the offical FIPS source
distribution tarballs.

Thus convert these files to UNIX line endings, matching the rest of the
repository.

Change-Id: If0f5835108a6b26bba5de0b6b950a69a4faa1410
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70307
Auto-Submit: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
4 files changed
tree: 371c9d90c1177ab909603d1d8912c0e6d9595728
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. gen/
  7. include/
  8. pki/
  9. rust/
  10. ssl/
  11. third_party/
  12. tool/
  13. util/
  14. .bazelignore
  15. .bazelrc
  16. .clang-format
  17. .gitignore
  18. API-CONVENTIONS.md
  19. BREAKING-CHANGES.md
  20. BUILD.bazel
  21. build.json
  22. BUILDING.md
  23. CMakeLists.txt
  24. codereview.settings
  25. CONTRIBUTING.md
  26. FUZZING.md
  27. go.mod
  28. go.sum
  29. INCORPORATING.md
  30. LICENSE
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. PORTING.md
  34. PrivacyInfo.xcprivacy
  35. README.md
  36. SANDBOXING.md
  37. 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: