| commit | a8d55075b50ff38facd17bb239246fdd3f169b2f | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Oct 28 16:23:07 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 28 20:38:22 2024 +0000 |
| tree | f75910fefb229df8668027d26047920d44d72957 | |
| parent | de6d1ca6ecb26e83ac9dbafd43f2e92b861e3963 [diff] |
Update Cargo.toml after the cfg rename Otherwise we get a bunch of warnings: > unexpected cfg condition name: bindgen_rs_file While I'm here, drop the authors field. It's no longer accurate as we've significantly reworked this from Android's original contribution. We could list the current maintainers, but that's redundant with the git repo, and bssl-crypto omits it, so let's just omit it. Change-Id: Ia1b60f1dfa4f4626b5fe2562f35a14ea0ce3aef5 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72627 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@google.com>
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: