From: "Mr. Aaron W. Swenson" <titanofold@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] Manifest signing
Date: Thu, 29 Sep 2011 16:48:35 +0000 [thread overview]
Message-ID: <20110929164834.GB32072@atlas> (raw)
In-Reply-To: <201109291223.09032.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]
On Thu, Sep 29, 2011 at 12:23:08PM -0400, Mike Frysinger wrote:
> On Thursday, September 29, 2011 11:11:59 Patrick Lauer wrote:
> > On 09/29/11 17:04, Tony "Chainsaw" Vroon wrote:
> > > On 29/09/11 16:02, Anthony G. Basile wrote:
> > >> Is there any chance that we can agree to reject
> > >> unsigned manifests? Possibly a question for the Council to adjudicate?
> > >
> > > I am happy to back a mandatory signing policy for the main gentoo-x86
> > > tree. This is a simple yes or no question that the council can vote on.
> >
> > As previously discussed it would be nice to have some basic key policies
> > in place for that - they can be changed at any later time, but for now
> > we could agree on basic parameters like, say -
> >
> > at least 1024bit key length
> > at least 6 months validity from creation
> > one or more algorithms (initially DSA signatures and SHA1 hashing)
>
> there's nothing to decide as it was already outlined long ago in the docs:
> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=6
>
> if you want to *refine* that, then that's a different issue. but the devs
> already have all the info they need to start signing now.
> -mike
Well, there's a bit more to it than that. 'repoman' must enforce the usage
of keys or die if it can't. Further, it needs to allow the selection of a
key if it can't determine which to use. I was hit by this last
night. Instead of dying and saying that I chose to sign but it couldn't
determine which secret key to use (I recently generated a new key), it
just disabled FEATURES="sign" and committed anyway.
Also, the Dev Handbook only says 'can', it needs to be changed to
'must'. I'd also drop the bit about expiration. Instead, I'd change it to
read "expires no sooner than 6 months". You know, to give the key a moment
to be recognized by some people, perhaps even marginally trusted by
someone. What really matters is that it is an unexpired, valid key.
--
Mr. Aaron W. Swenson
Pseudonym: TitanOfOld
Gentoo Developer
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-09-29 16:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E848879.2050100@gentoo.org>
2011-09-29 15:04 ` [gentoo-project] Re: [gentoo-dev] Manifest signing Tony "Chainsaw" Vroon
2011-09-29 15:11 ` Patrick Lauer
2011-09-29 15:48 ` Rich Freeman
2011-09-29 16:09 ` Tony "Chainsaw" Vroon
2011-09-29 16:18 ` Anthony G. Basile
2011-09-29 16:31 ` Mike Frysinger
2011-09-29 16:59 ` Mr. Aaron W. Swenson
2011-09-29 17:17 ` Mike Frysinger
2011-09-29 16:23 ` Mike Frysinger
2011-09-29 16:36 ` Anthony G. Basile
2011-09-29 16:38 ` Anthony G. Basile
2011-09-29 16:48 ` Mr. Aaron W. Swenson [this message]
2011-09-29 17:26 ` Mike Frysinger
2011-09-29 17:56 ` Mr. Aaron W. Swenson
2011-09-29 16:28 ` Ciaran McCreesh
2011-09-29 19:43 ` Robin H. Johnson
2011-09-29 20:00 ` Markos Chandras
2011-09-29 20:57 ` 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=20110929164834.GB32072@atlas \
--to=titanofold@gentoo.org \
--cc=gentoo-project@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