2026-08-07 08:39 UTC
Replies (2)
-
@naderman@phpc.social 2026-08-07 08:43
@heiglandreas@phpc.social @kleisli@mastodon.social @OndrejMirtes@phpc.social @markusstaab@phpc.social @toflar@phpc.social No, you want SLSA build provenance attestations and in a perfect world a reproducible build: https://phpc.social/@naderman/117053334241906529
-
@timwolla@phpc.social 2026-08-07 09:26
@heiglandreas@phpc.social @kleisli@mastodon.social @naderman@phpc.social @OndrejMirtes@phpc.social @markusstaab@phpc.social @toflar@phpc.social Long-lived secrets are a liability. In particular both a PGP signature created with a key stored your CI/CD runner and a PGP signature created with a key on your local machine that was hit by the latest hijacked npm / Composer / Cargo / … package is strictly worse than a SLSA build provenance attestation stored in a transparency log.