Re: Expired GPG keys of older release
- Date: Sat, 23 Jun 2018 08:58:47 +0200
- From: <tomas@xxxxxxxxxx>
- Subject: Re: Expired GPG keys of older release
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, Jun 22, 2018 at 11:48:00PM -0500, David Wright wrote:
> On Fri 22 Jun 2018 at 21:12:51 (+0200), tomas@xxxxxxxxxx wrote:
> Well, I attempted to supply that in
> but I have no idea whether that would be achievable in docker
> or not because the suggestion has had no follow-up.
I'm not the docker guy, and there are lots of "interesting" things
around, so I won't be the one. But I'm curious too...
> BTW Reading your "Keys *have* to expire at some point, and you can't
> re-sign archived packages with a fresh key", it's not clear why the
> expired key can't be unexpired, ie given an expiration date in the
> future, if it's known to be still good.
Yes, you're right: a GPG key's validity can be extended with a new
certificate (whether it's responsible to do is another thing, since
available computing power grows, *and* there has been more time to
hack at this key, its crypto, and for things to leak). So practically
speaking still keys have to expire at some point.
The only way out would be for an archive declared immutable to set
up an attestation service which signs (state-of-the-art) package
hashes with (state-of-the-art) signing procedures and refreshes
things periodically. Debian hasn't decided to set that up, a thing
I can understand.
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----