| commit | 3002573119a976c0dc968f04f57951f4aa335fe1 | [log] [tgz] |
|---|---|---|
| author | Bob Beck <bbe@google.com> | Tue Mar 14 16:58:32 2023 -0600 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 15 18:29:23 2023 +0000 |
| tree | fe3239847a4cf03f8df60f39f1eb2bd7e1e798e6 | |
| parent | 8c7aa6bfcd7573d7b904fde6acb4f3652a3ebecc [diff] |
Hmac should be able to take longer keys HMAC hashes long keys internally using the provided hash function. This removes the arbitrary limit of EVP_MAX_MD_SIZE on the length of the key. Change-Id: I56d68cbd2ddaf1f5f1fa4ecc40105b00b2ccd87c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/58006 Reviewed-by: Nabil Wadih <nwadih@google.com> Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: 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: