Google Git
Sign in
boringssl / boringssl / dbbd79e89526f68589064e488b900cb1aedd7422
commitdbbd79e89526f68589064e488b900cb1aedd7422[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Jan 25 15:38:19 2023 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 25 21:02:24 2023 +0000
treef05ded5cac86a497d8ea4e25da95aa263542884c
parenteefe6cf27cad9f8303743208f3886cc3f128de53 [diff]
Add a WORKSPACE.toplevel file

The WORKSPACE file in master-with-bazel is currently synthesized by the
script. If we end up with something like
https://boringssl-review.googlesource.com/c/boringssl/+/55965, we'll
need to be able to change it more easily. Make it the same way as
BUILD.

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