commit | 1f0dd667d447da8d96f6ce3b4b3dd78ad09fda65 | [log] [tgz] |
---|---|---|
author | Elly <ellyjones@chromium.org> | Fri Apr 18 00:49:39 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 18 00:49:39 2025 |
tree | ef95dc6eae703229a2d9ea6ede71bfb4f325a5f9 | |
parent | 3cb6a9381f33996faa55218534eaefb2c80853f0 [diff] |
components/metrics: migrate to new crypto APIs Specifically, crypto/hash instead of crypto/sha2 and the new crypto/hmac API. This change also alters UnsentLogStore::ComputeHMACForLog(). This API used to return a bool to indicate that computing the HMAC had failed, which some calling code (such as the unit tests) appeared to believe indicated that the provided key was invalid. Actually, HMAC signing with the old HMAC API could never fail - an empty key would simply be padded with zero bytes out to the required length - so this function could never return false in practice. This change swaps the API to returning the signature value directly instead of returning a success flag that can never be false. Bug: 372283556 Change-Id: Ib99cf524462a84f6970337d3a744bf539e5451a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6461094 Reviewed-by: Sergio Collazos <sczs@chromium.org> Reviewed-by: Robert Kaplow <rkaplow@chromium.org> Commit-Queue: Elly FJ <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/main@{#1448696}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.