From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] Manifest signing
Date: Thu, 29 Sep 2011 21:00:39 +0100 [thread overview]
Message-ID: <4E84CE67.60202@gentoo.org> (raw)
In-Reply-To: <robbat2-20110929T194209-257387404Z@orbis-terrarum.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 09/29/11 20:43, Robin H. Johnson wrote:
> On Thu, Sep 29, 2011 at 05:11:59PM +0200, Patrick Lauer wrote:
>> Another point: Currently we do NOT sign eclasses and profiles. So
>> before such a policy becomes mandatory we need to figure out how
>> to handle that, otherwise we can't enforce it
> And this is EXACTLY why I wrote the tree-signing GLEPS.
>
> MetaManifest solves the problem over covering the entire tree with
> signatures, WITHOUT requiring any specific action from developer.
>
Robin,
I presume you are talking about GLEP 58[1] which seems to depend on
GLEP{59,60,61}[2][3][4]. Is that correct? So before we get to
MetaManifest we need to push the implementation for the rest of the
GLEPs forward
[1]http://www.gentoo.org/proj/en/glep/glep-0058.html
[2]http://www.gentoo.org/proj/en/glep/glep-0059.html
[3]http://www.gentoo.org/proj/en/glep/glep-0060.html
[4]http://www.gentoo.org/proj/en/glep/glep-0061.html
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJOhM5nAAoJEPqDWhW0r/LCkksP/R6SPLFxURHhXEXh1uyWBj5/
C3qsYUPywH0P49IEYMLsMj8kmw08+wqIiK1vNljyIBPidltFQM6EFkjDjxo5m5ZV
oC9LgyHuSnIqo8FImh20TDuANhJHLQ4NdTXEYV3uTfV7LziL3t/WdQ+skviVR27Z
mPPPrGPfCUuXIuVVgqvzRDQiPWvaeRuGIKRNMcYEUjiBS4JpF03yPpQ3QQFKVQYp
EL4cryqw7bvTOpJ/AT+wV20N06/bEn1Tru/Qk9tWrEIUsleJzkVDwT31UnforETj
2Z2UY3UBMEoLaJnvmYmMuZBmVXl+xJ5PKhBhEMAC5HaExp7ACzKbhsxtULc2MGAo
y7i6dHLPPClWAGeVjt7XwLnqf/acylLFM5gV2HqL20fJafSeGW+MxMDnK1xRlyc0
4/HJrbUZp58MY0AcGuidNz2yzr6VPG+wydZdsdZrcjjoJmoqS2LC8KJOF6FgP4qP
BQrxgGy1g+F1YM+MBePcrsyLpZgnLrkbacXDg87neNejgfZXMjWPQxqMBS+4y185
t/AI7NShufZcEPztd9dFrieK9xMBJoO6ussUkba5zw00yNSyAXR255vnYK0Onqb6
/aBvCH3Zui1S96MMZ8KLBmubRav+mJrMJ1icQDBFjEgtwMJlILcUap0bJDphS8fp
cNHDLzUNYe6PPAGLEiSf
=EE/a
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-09-29 20:01 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
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 [this message]
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=4E84CE67.60202@gentoo.org \
--to=hwoarang@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