public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Tree Integrity GLEPS for final review and council approval
Date: Tue, 1 Dec 2009 01:08:52 +0000	[thread overview]
Message-ID: <20091201010852.GB1158@orbis-terrarum.net> (raw)
In-Reply-To: <20091130113051.GA32489@chopin.edu.pl>

[-- Attachment #1: Type: text/plain, Size: 2490 bytes --]

On Mon, Nov 30, 2009 at 12:30:51PM +0100, Antoni Grzymala wrote:
> I reckon that missing GPG infrastructure is one of the greatest problems
> of the Gentoo distribution esp. regarding serious corporate and academic
> deployments.
> 
> I can devote some time to helping with the matter.
I would certainly like to get that GLEP series completed and out there.

There are still two GLEPs in the series that have not yet made it to
draft status:
http://sources.gentoo.org/viewcvs.py/gentoo/users/robbat2/tree-signing-gleps/02-developer-process-security
http://sources.gentoo.org/viewcvs.py/gentoo/users/robbat2/tree-signing-gleps/03-gnupg-policies-and-handling

However the main content of GLEPS 58-61 IS ready for the council to
approve, and are NOT blocking on the above two items.

As such, I would like to present GLEPS 58,59,60,61 for final review, and
for the council to vote on their approval during the January meeting.

I'm going to summarize them here:
GLEP58: Security of distribution ... MetaManifest 
-------------------------------------------------
- covers all Manifests with a infra-generated parent Manifest.
- required for end-to-end validation.
- prevents certain package manager attacks.
- NO day-to-day developer actions required.

GLEP59: Manifest2 hash policies and security implications 
---------------------------------------------------------
- Add SHA512 to all Manifest files.
- Schedule removal of SHA1, MD5, RMD160 for 6-18 months after SHA512
  addition.
- Be prepared to add the NIST hash contest candidates/winner.

GLEP60: Manifest2 filetypes
---------------------------
(Has one TODO that needs clarification).
- Breaks down the Manifest2 filetypes into INFOrmational and CRITical.
- If the package manager is being strict, then INFO filetypes are
  treated as CRIT filetypes.
- INFO filetypes merely cause a warning on absence.
- CRIT filetypes may trigger a delayed OR immediate failure of absence.

GLEP61: Manifest2 compression
-----------------------------
- Disk space optimization for MetaManifest from GLEP58.

There is a prototype of the MetaManifest code here:
http://sources.gentoo.org/viewcvs.py/gentoo/users/robbat2/tree-signing-gleps/prototype/
It worked on Portage 2 years ago, but I haven't run it since then.

-- 
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

[-- Attachment #2: Type: application/pgp-signature, Size: 330 bytes --]

  parent reply	other threads:[~2009-12-01  1:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 21:50 [gentoo-dev] Next council meeting on 7 Dec 2009 at 1900UTC Denis Dupeyron
2009-11-26  1:34 ` Brian Harring
2009-11-26  1:39   ` Zac Medico
2009-11-26 15:31   ` Ciaran McCreesh
2009-11-26 16:33     ` Brian Harring
2009-11-26 16:46       ` Ciaran McCreesh
2009-11-27  8:08         ` Brian Harring
2009-11-30 11:30 ` Antoni Grzymala
2009-11-30 11:41   ` Antoni Grzymala
2009-11-30 21:18   ` [gentoo-dev] GPG Infrastructure for Gentoo (Was Council Meeting) Richard Freeman
2009-11-30 22:28     ` Dawid Węgliński
2009-12-01  1:27     ` Robin H. Johnson
2009-12-03 10:32       ` [gentoo-dev] Individual developer signing Torsten Veller
2009-12-03 12:51         ` Thilo Bangert
2009-12-03 20:35         ` Robin H. Johnson
2009-12-11 16:32           ` [gentoo-dev] " Torsten Veller
2009-12-01  1:08   ` Robin H. Johnson [this message]
2009-11-30 17:57 ` [gentoo-dev] Next council meeting on 7 Dec 2009 at 1900UTC Thomas Sachau

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=20091201010852.GB1158@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