| commit | a4c3f8de4406c2382e43e88a638882fb1a32da32 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jan 18 18:06:58 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 22 19:14:08 2024 +0000 |
| tree | f4c723f9a69b1545ea567d5bd0dc1fbb4154f9da | |
| parent | 672efb1f8ee029762e29ff16811b68a071a0528e [diff] |
Document assumptions made by bssl-crypto's unboxed HMAC_CTX I believe it is currently fine, but we probably should either box it, or get to the point that the assumptions are less precarious. Rust FFI is anything but safe. Bug: 682 Change-Id: I4b45dd3c3f58fb0ce7c0b8b80b1e6d7d2f7f119f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65627 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@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:
There are other files in this directory which might be helpful: