Add templates for Publish to BCR

Not sure if these are correct. I added a README so that our future
selves have some hope of figuring out what this is for. The metadata and
presubmit files I copied from our existing BCR entries.

https://github.com/bazelbuild/bazel-central-registry/blob/main/modules/boringssl/0.0.0-20240530-2db0eb3/presubmit.yml
https://github.com/bazelbuild/bazel-central-registry/blob/main/modules/boringssl/metadata.json

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