Google Git
Sign in
boringssl / boringssl / 2896aa9ca0ca7b8887ed022b7e8bef97b30e88e7
commit2896aa9ca0ca7b8887ed022b7e8bef97b30e88e7[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Mar 10 22:37:04 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 02 15:00:31 2025 -0700
tree254c53c45a5025521a9a3927d067fb985bfcc496
parentdcfdef8af80f677a2ab5bada6fc6bead4b1772cf [diff]
Spell Apache 2.0 correctly in fiat/README.chromium

Looks like it's meant to have a hyphen, to match the SPDX identifier.

https: //source.chromium.org/search?q=License%5C:%5C%20Apache%20file:README.chromium&sq=&ss=chromium
https: //chromium.googlesource.com/chromium/src/+/HEAD/docs/adding_to_third_party.md#add-a-license-file-and-run-related-checks
Change-Id: I553cb40dc0ef55a7a3634ac2488f389e1ed47dfc
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77288
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: 254c53c45a5025521a9a3927d067fb985bfcc496
  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: