From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Signing everything, for fun and for profit
Date: Sat, 20 May 2006 15:10:40 +0200 [thread overview]
Message-ID: <1148130640.6290.34.camel@localhost> (raw)
In-Reply-To: <446ECF96.9090607@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]
On Sat, 2006-05-20 at 10:13 +0200, Thierry Carrez wrote:
> Patrick Lauer wrote:
>
> > Signing strategies
> > ==================
> >
> > Once there is an agreement on what files to sign with what kind of keys
> > there remains the question how to sign it. There are at least three
> > strategies:
> > [...]
>
> I prefer a semi-secure solution appearing soon rather than waiting
> another three+ years for a potentially better solution.
A staged plan might be best then:
- implement a simple master-key signing
- discuss the more complex distributed models
- implement the distributed models if agreed upon
> Currently users only have two choices :
>
> - masterkey-signed portage snapshots
> - unsigned (and so, insecure) rsync mirrors
>
> This is obviously not satisfying.
Yes. It also gives us ~100 single points of attacks as every compromised rsync mirror could go undetected for a long time.
> It has taken years to try to get per-developer signing implemented,
> without success. We should try to do masterkey signing ("simple" method)
> and see if we go somewhere. It's is so much better than nothing.
There is no authority that "forces" signing.
Making signing mandatory should not cause big problems now ...
> So I would rather work on ensuring everything in portage gets properly
> signed rather than designing key policies, cross-signing strategies and
> ways to force developers to sign properly. Given the current state of
> Gentoo it is a much more reachable goal.
"properly signed" implies some standard or policy to measure it against.
So we need to have some agreement what is needed to assure "properly
signed everything" - it looks like the centralized masterkey model will
have the smallest impact on all involved. Then we look at all issues
this model has, try to fix all bugs - then we have a plan to implement,
and I hope that this will happen in a reasonable timeframe.
Patrick
--
Stand still, and let the rest of the universe move
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2006-05-20 13:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 21:45 [gentoo-dev] Signing everything, for fun and for profit Patrick Lauer
2006-05-18 23:53 ` Kevin F. Quinn
2006-05-18 23:54 ` Ciaran McCreesh
2006-05-19 4:26 ` Robin H. Johnson
2006-05-20 2:03 ` Ned Ludd
2006-05-20 13:03 ` Patrick Lauer
2006-05-20 13:21 ` Jan Kundrát
2006-05-20 20:47 ` Robin H. Johnson
2006-05-21 10:40 ` Paul de Vrieze
2006-05-19 9:46 ` Chris Bainbridge
2006-05-19 11:20 ` Patrick Lauer
2006-05-19 14:13 ` Chris Bainbridge
2006-05-19 14:39 ` Andrew Gaffney
2006-05-19 15:17 ` Chris Bainbridge
2006-05-19 15:26 ` John Myers
2006-05-19 16:10 ` Chris Bainbridge
2006-05-19 13:30 ` Thomas Cort
2006-05-20 6:30 ` Alin Nastac
2006-05-19 15:32 ` Chris Gianelloni
2006-05-19 15:35 ` Harald van Dijk
2006-05-19 15:26 ` Patrick Lauer
2006-05-19 16:06 ` Chris Bainbridge
2006-05-19 16:50 ` Marius Mauch
2006-05-19 17:04 ` Harald van Dijk
2006-05-19 16:28 ` [gentoo-dev] " Peter
2006-05-19 16:41 ` Chris Bainbridge
2006-05-19 16:51 ` Stephen Bennett
2006-05-19 17:26 ` Marius Mauch
2006-05-20 5:44 ` Lance Albertson
2006-05-19 17:45 ` [gentoo-dev] " Marius Mauch
2006-05-20 8:13 ` Thierry Carrez
2006-05-20 13:10 ` Patrick Lauer [this message]
2006-05-20 10:54 ` [gentoo-dev] " Peter
2006-05-20 14:37 ` Chris Bainbridge
2006-05-20 14:51 ` [gentoo-dev] " Peter
2006-05-21 11:31 ` Chris Bainbridge
2006-05-21 13:49 ` Francesco Riosa
2006-05-20 23:48 ` [gentoo-dev] " 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=1148130640.6290.34.camel@localhost \
--to=patrick@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