2026-08-07 09:47 UTC
@phpcs@phpc.social @heiglandreas@phpc.social @kleisli@mastodon.social @naderman@phpc.social @OndrejMirtes@phpc.social @markusstaab@phpc.social @toflar@phpc.social
It is possible to update the expiry of a PGP key without changing its ID. Users would need to fetch the key with the updated expiry, but could continue verifying against their trusted fingerprint.
see: https://mhdez.com/notes/renewing-an-expired-gpg-key/
Replies (1)
-
@phpcs@phpc.social 2026-08-07 18:05
@timwolla@phpc.social @heiglandreas@phpc.social @kleisli@mastodon.social @naderman@phpc.social @OndrejMirtes@phpc.social @markusstaab@phpc.social @toflar@phpc.social TIL. For now - with the fact that we already do SLSA attestations and all builds are reproducible in mind -, I've followed @edorian@phpc.social's advice to set the expiry date to 5 years. The primary reason to still do GPG signing is PHIVE and there is an issue open (and has been for two years) about PHIVE verifying SLSA attestations: https://github.com/phar-io/phive/issues/429 I'm hoping once the five years are up, it will be a solved problem.