From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [pre-GLEP r1] Gentoo binary package container format
Date: Mon, 19 Nov 2018 20:48:37 +0000 [thread overview]
Message-ID: <C2ZZd8PMT+1+PM0M5v5Wm5@uDsTzkKaXS5JM7acFCZXU> (raw)
In-Reply-To: <CAGfcS_k8c-s=sjJWkQFfQjhRD7KXYeHK71OTR9cfE94zfurxVw@mail.gmail.com> (from rich0@gentoo.org on Mon Nov 19 19:33:17 2018)
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
On 2018.11.19 19:33, Rich Freeman wrote:
> On Mon, Nov 19, 2018 at 2:21 PM Roy Bamford <neddyseagoon@gentoo.org>
> wrote:
> >
> > "The archive members support optional OpenPGP signatures.
> > The implementations must allow the user to specify whether OpenPGP
> > signatures are to be expected in remotely fetched packages."
> >
> > Or can the user specify that only some elements need to be signed?
> >
> > Is it a problem if not all elements are signed with the same key?
> > That could happen if one person makes a binpackage and someone
> > else updates the metadata.
> >
>
> IMO this is going a bit into PM details for a GLEP that is about
> container formats.
>
Rich,
Not really. The GLEP needs to be clear about the signing.
Is it every element or none?
The GLEP hints that a mix of is possible with
If the implementation needs to manipulate archive members, it must
either create a new signature or discard the existing signature.
An individual binpackage could start life with all elements signed
by the same key.
Some element could be updated and the key for the signature of
that element changed.
Later still, another element can be changed an have its signature
dropped.
Should some combinations have no practical value, they should
not be permitted by the GLEP.
> --
> Rich
>
>
>
--
Regards,
Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-19 20:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 11:21 [gentoo-dev] [pre-GLEP] Gentoo binary package container format Michał Górny
2018-11-17 14:05 ` Roy Bamford
2018-11-17 14:17 ` Rich Freeman
2018-11-17 21:53 ` Michał Górny
2018-11-18 9:16 ` Fabian Groffen
2018-11-18 9:38 ` Michał Górny
2018-11-18 11:00 ` Fabian Groffen
2018-11-19 20:46 ` Kent Fredric
2018-11-21 9:33 ` Michał Górny
2018-11-21 10:45 ` Fabian Groffen
2018-11-21 11:20 ` Michał Górny
2018-11-26 21:13 ` Andrey Utkin
2018-11-27 8:32 ` Fabian Groffen
2018-11-18 11:04 ` Roy Bamford
2018-11-19 18:35 ` [gentoo-dev] [pre-GLEP r1] " Michał Górny
2018-11-19 19:21 ` Roy Bamford
2018-11-19 19:33 ` Rich Freeman
2018-11-19 19:40 ` Zac Medico
2018-11-19 19:51 ` Rich Freeman
2018-11-19 20:48 ` Roy Bamford [this message]
2018-11-20 20:34 ` Michał Górny
2018-11-20 20:33 ` [gentoo-dev] [pre-GLEP r2] " Michał Górny
2018-11-21 13:10 ` Fabian Groffen
2018-11-21 14:21 ` Michał Górny
2018-11-26 18:58 ` [gentoo-dev] [pre-GLEP r3] " Michał Górny
2018-11-26 19:17 ` Ulrich Mueller
2018-11-26 19:51 ` Michał Górny
2018-11-26 21:43 ` Roy Bamford
2018-11-30 17:06 ` Michał Górny
2018-11-30 21:23 ` Roy Bamford
2018-11-30 17:09 ` [gentoo-dev] [pre-GLEP r4] " Michał Górny
2018-12-01 10:25 ` Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C2ZZd8PMT+1+PM0M5v5Wm5@uDsTzkKaXS5JM7acFCZXU \
--to=neddyseagoon@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox