| commit | 79916924b315f9b81bf5eefce6fae598b77c70b9 | [log] [tgz] |
|---|---|---|
| author | Nabil Wadih <nwadih@google.com> | Fri May 19 09:04:11 2023 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 16 20:12:37 2023 +0000 |
| tree | 2f803db55c1628e05ebce8704eb9e86c184abbf4 | |
| parent | ac45226f8d8223d70ed37cf81df5f03aea1d533c [diff] |
Add rust bindings to AES-GCM-SIV through the EVP_AEAD_* API's Implemented a generic Aead trait and struct against the EVP_AEAD API's, which can be used to provide bindings to all of the AEAD's provided by boringssl. Starting with AES_GCM_SIV, but will expand to more AEAD's. Change-Id: I7d4113f3d49ff40de3ccb76424f9a25d25797e82 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/59965 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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:
There are other files in this directory which might be helpful: