From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Manifest signing
Date: Thu, 29 Sep 2011 19:36:22 +0000 [thread overview]
Message-ID: <robbat2-20110929T192830-577785968Z@orbis-terrarum.net> (raw)
In-Reply-To: <pan.2011.09.29.19.08.29@cox.net>
On Thu, Sep 29, 2011 at 07:08:29PM +0000, Duncan wrote:
> Beyond that, IMO it's now at the "needs a proposal champion to clean it
> up and present it to the council" stage, at least at the "council
> declared priority" level for getting the requirements into repoman, the
> CVS server, and perhaps the PMs (I don't know what stage they're at,
> possibly all they need is a switch flipped?).
It doesn't need cleaning up. I wrote the tree-signing GLEPs a few years
ago, and those were approved by the council, really they just need
updating to a recent Portage and usage.
They provide better support than just getting every developer to sign
the Manifests, because to do so while eclasses are unsigned is a giant
security hole. MetaManifest in the proposal covers that by getting the
entire tree to a state of being signed.
> Talking about which, at the PM user level, is there a per-repo/overlay
> switch? If not, it should strongly be considered.
Yes. See layout.conf/repo.conf. Also controls usage of thin Manifests.
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
next prev parent reply other threads:[~2011-09-29 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 15:02 [gentoo-dev] Manifest signing Anthony G. Basile
2011-09-29 15:04 ` Tony "Chainsaw" Vroon
2011-09-29 15:09 ` Fabian Groffen
2011-09-29 19:08 ` [gentoo-dev] " Duncan
2011-09-29 19:36 ` Robin H. Johnson [this message]
2011-11-02 12:03 ` [gentoo-dev] " enno+gentoo
2011-11-02 16:11 ` Robin H. Johnson
2011-11-03 21:55 ` enno+gentoo
2011-11-03 23:09 ` Robin H. Johnson
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=robbat2-20110929T192830-577785968Z@orbis-terrarum.net \
--to=robbat2@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