Andrew Nesbitt 61741123bf Verify cached artifacts on read (#111) ... checkCache opened the storage reader and streamed it to the client without checking that the bytes still matched what was originally stored, or what the upstream registry declared. Disk corruption, accidental overwrites, or local tampering would go unnoticed. Wrap the storage reader in a verifyingReader that computes SHA256 (against artifact.content_hash) and, when version.integrity holds an SRI string, the corresponding sha256/384/512 digest as bytes flow through. At EOF the digests are compared; on mismatch we log at error level, bump proxy_integrity_failures_total, and clear the artifact's cache entry so the next request refetches from upstream. Verification is skipped when the stream was not fully consumed (client disconnect) to avoid evicting good artifacts on partial reads. The DirectServe presigned-URL path is unverified since the proxy never sees those bytes. Refs #42 (part 1)		2026-05-03 10:36:28 +01:00
..
metrics.go	Verify cached artifacts on read (#111)	2026-05-03 10:36:28 +01:00
metrics_test.go	Apply 'go fmt' as suggested in CONTRIBUTING.md.	2026-04-18 07:43:22 -04:00