-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Description
Request
Please publish SHA-256 checksums and/or GitHub artifact attestations alongside release binaries.
Why
Currently the release assets include only bare binaries with no mechanism for downstream consumers to verify integrity or provenance. Projects that install cloudflared from GitHub releases have to either:
- Hardcode SHA-256 checksums and manually update them every release (brittle)
- Skip verification entirely (insecure)
A checksums file (e.g., cloudflared-checksums-sha256.txt) in the release assets would be a quick win. Artifact attestations would be even better, enabling cryptographic provenance verification with:
gh attestation verify cloudflared-linux-amd64 --repo cloudflare/cloudflaredContext
We ran into this while adding supply-chain hardening to NVIDIA/NemoClaw, which downloads cloudflared in its install scripts. We're currently hardcoding checksums as a workaround.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels