From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] Manifest signing
Date: Thu, 29 Sep 2011 12:38:19 -0400 [thread overview]
Message-ID: <4E849EFB.1020101@gentoo.org> (raw)
In-Reply-To: <4E849E7A.5000104@gentoo.org>
On 09/29/2011 12:36 PM, Anthony G. Basile wrote:
> On 09/29/2011 12:23 PM, 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
> Thanks I didn't know that had made it to the devmanual. I drop my
> original request.
>
> I guess the next step, if we were to take it, would be to have infra
> enforce the policy automatically if a commit comes in which isn't signed.
>
Sorry sent this before getting Mike's email about
https://bugs.gentoo.org/377233
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 8040 5A4D 8709 21B1 1A88 33CE 979C AF40 D045 5535
GnuPG ID : D0455535
next prev parent reply other threads:[~2011-09-29 16:38 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 [this message]
2011-09-29 16:48 ` Mr. Aaron W. Swenson
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=4E849EFB.1020101@gentoo.org \
--to=blueness@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