On Tue, 2020-10-06 at 18:17 +0000, Robin H. Johnson wrote: > While I'm absolutely in favour of the overall intent here, I'm not so > sure of the design. > > I'm worried about the proliferation of tiny packages just to convey the > keys; and how versioning should work if upstream rotates their keys. > I picked this message in the thread to respond to, because it was > clearest that this could break when the keys are rotated. The old > releases might not be verifiable with the new keys. > > Additionally: > - not all upstream providers ship .asc files of their keys > - some upstreams use signed DIGESTS files rather than directly signing > the distfiles (esp. where distfiles are larger) > > Can we instead: > Inside the ebuild and/or metadata.xml: convey: > 1. URL(s) to fetch keys, incl a keyserver support > 2. Full key fingerprint
It won't work inside network-isolated environments. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
