2026-08-07 09:30 UTC
@heiglandreas@phpc.social @kleisli@mastodon.social @naderman@phpc.social @OndrejMirtes@phpc.social @markusstaab@phpc.social @toflar@phpc.social
And not to throw shade on them, since they already do SLSA attestations (https://github.com/PHPCSStandards/PHP_CodeSniffer/attestations), but I quite enjoyed that @phpcs@phpc.social apparently rotated their PGP key for their 4.0.2 security release: https://github.com/PHPCSStandards/PHP_CodeSniffer/releases/tag/4.0.2
> The GPG signature for the PHAR files has been rotated. The new fingerprint is: 5CB4F778BF9BC4FB67AE511D96E91A992CF22FF4.
Replies (1)
-
@timwolla@phpc.social 2026-08-07 09:32
@heiglandreas@phpc.social @kleisli@mastodon.social @naderman@phpc.social @OndrejMirtes@phpc.social @markusstaab@phpc.social @toflar@phpc.social @phpcs@phpc.social Doing a key rotation for a security release would be a perfect opportunity for an attacker to sneak in a new signing key, since folks are likely to be less diligent when their security scanners are breathing down their neck: They would need to decide between fixing the security issue and properly verifying that the key rotation is legit.