From da74882bfe0a3cf57e2d4d0a4bbd726652879587 Mon Sep 17 00:00:00 2001 From: Patrick McDermott Date: Sun, 24 Jun 2018 22:27:14 -0400 Subject: dev/archive/signing: Consider not distributing keys with prokit Rely on existing PKI and leave keyring management to users. --- diff --git a/dev/archive/signing.mdwn b/dev/archive/signing.mdwn index e7d6168..0dfd6be 100644 --- a/dev/archive/signing.mdwn +++ b/dev/archive/signing.mdwn @@ -39,6 +39,15 @@ key(s) into their keyring. If keys are distributed with prokit, **revocations and key transitions need to be handled somehow**. +A user already has to import a key into their own keyring to verify their prokit +download. Maybe it's better to just instruct users to also download the archive +signing key(s) into their keyrings. This takes advantage of existing PKI, and +leaves users to make sure their keyring is kept updated with signatures, +revocations, changed expiration dates, and transitions. It also avoids having +released prokit versions "expire" due to included keys expiring. + +Suggestions welcome. + Opkg ---- -- cgit v0.9.1