Skip to content

fix(common): use cryptographically secure SHA-256 for transfer cache key generation #69177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
atscott merged 1 commit into from
Jun 5, 2026
+306 −116

fix(common): use cryptographically secure SHA-256 for transfer cache …

270e1a4
Select commit
Loading
Failed to load commit list.
Merged

fix(common): use cryptographically secure SHA-256 for transfer cache key generation #69177

fix(common): use cryptographically secure SHA-256 for transfer cache …
270e1a4
Select commit
Loading
Failed to load commit list.
Google CLA / cla/google succeeded Jun 5, 2026 in 7s

✅ All contributors are covered under a CLA with Google

See https://cla.developers.google.com/ for more info about Google's Contributor License Agreement (CLA).

ℹ️ Googlers: Go here to view more details and manage scans for this pull request.

Details

The following contributors were found for this pull request:

✅ 270e1a4 Author: @alan-agius4 <17563226+alan-agius4​@users.noreply.github.com>

(Only the first commit for a unique contributor is listed.)

View more details on Google CLA