From: Chris Haumesser <ch@awry.ws>
To: gentoo-security@lists.gentoo.org
Subject: Re: [gentoo-security] Re: Out of air
Date: Tue, 09 Nov 2004 20:53:21 -0800 [thread overview]
Message-ID: <41919EC1.5010809@awry.ws> (raw)
In-Reply-To: <20041109233509.A19723@netdirect.ca>
[-- Attachment #1: Type: text/plain, Size: 3452 bytes --]
Finally, a message I can fully agree with.
As there is a quick and dirty solution to improve the situation -- even
with the understanding that it is not the "best" or "ideal" solution --
I would encourage the gentoo devs to implement it. It really doesn't
seem like rocket science.
I do consider it a significant problem that I cannot accurately verify
that everything in my portage tree came from a trusted source. Agreed,
MOTM attacks are not common. However, it would seem important to have
some sort of "audit trail" to verify that portage is what it's supposed
to be. Not only is this good proactive security, but it might also
prove useful in tracking the source of some security problem.
An interim signing solution, as mentioned already in this list, would
provide at least a mechanism (maybe not a great one, but one
nonetheless) by which a user can verify that the files downloaded to his
gentoo machine are those the developers intended to distribute.
I trust the devs implicitly, but I do not trust, nor can I control, most
of the points between them and me.
I think ultimately the existing plan, to implement full gpg signing of
each file in portage, is definitely the way to go. In the meantime,
while the infrastructure is laid for the superior, longterm proposal,
why not spend an hour to provide an interim, if not ideal, solution?
Devs, what have you to lose by helping us do this? I don't think I
understand the resistance, outside of the emotional reaction triggered
by this thread's initiator.
My $.02.
-C-
Chris Frey wrote:
>On Tue, Nov 09, 2004 at 09:05:41PM -0500, Denis Roy wrote:
>
>
>>>not prompted the beginning of a new initiative in signing the tree
>>>
>>>
>>because that was already underway. I very much doubt that it'll speed
>>up the progress made on that initiative, because the main limiting
>>factor is time. No matter what is said here, it's not going to make
>>anybody go out and quit their jobs in order to get tree signing
>>implemented quicker.
>>
>>
>
>The problem with phrasing it this way is that it implies there is only
>one way to address this issue. It may be true that Gentoo has decided
>on only one way to address the issue, but there are other ways to do it.
>
>The current development effort that is underway is not one that can be
>implemented overnight, but there is a solution that manages to satisfy
>the core needs of this thread that can be implemented overnight.
>
>The requirements are:
>
> * admin access on the main Gentoo server
> * a cron job
> * a GPG key on the server
> * a script to do the heavy lifting
>
>Of those items, only the script can be written by us normal users,
>in order to help out in the Open Source way. The people with admin
>access to the main Gentoo server do not appear willing to install such
>a script, even if someone else writes it. (And I'm sure Peter would
>jump at the chance to write it, and practically has already, and I'd
>definitely be willing to help.)
>
>I asked this before, and saw no response, so maybe it was missed in the
>pile of messages. I'll ask again:
>
> If someone posted a working and self-tested script to this mailing
> list, would Gentoo admins be willing to install it, provided it
> passed the peer review on this list? (i.e. contained no glaring bugs)
>
>If the answer was yes, this thread would be over.
>
>- Chris
>
>
>--
>gentoo-security@gentoo.org mailing list
>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-11-10 4:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 2:05 [gentoo-security] Out of air Denis Roy
2004-11-10 4:35 ` [gentoo-security] " Chris Frey
2004-11-10 4:53 ` Chris Haumesser [this message]
2004-11-10 5:08 ` Jason Stubbs
2004-11-10 7:02 ` Chris Haumesser
2004-11-10 7:04 ` Chris Haumesser
2004-11-10 7:22 ` Marius Mauch
2004-11-10 10:03 ` Dominik Schäfer
2004-11-10 13:52 ` [gentoo-security] The solution and hopefully the end Kurt Lieber
2004-11-10 14:00 ` Anthony Metcalf
2004-11-10 14:24 ` [gentoo-security] " Chris Frey
2004-11-10 18:15 ` [gentoo-security] " Gary Nichols
2004-11-10 19:02 ` Joey McCoy
2004-11-10 19:20 ` Michael Gruenberger
2004-11-10 19:57 ` Joey McCoy
2004-11-10 21:22 ` Glen Combe
2004-11-10 21:57 ` William Barnett
2004-11-10 19:26 ` DeadManMoving
2004-11-10 22:17 ` [gentoo-security] " Thomas Kirchner
2004-11-10 22:20 ` Jeff Smelser
2004-11-10 22:26 ` dan
2004-11-10 23:42 ` [gentoo-security] " Thomas Kirchner
2004-11-11 1:16 ` [gentoo-security] " James A. Cox
2004-11-11 1:19 ` Jason Stubbs
2004-11-11 5:45 ` [gentoo-security] " Peter Simons
2004-11-11 8:41 ` [gentoo-security] just can't let it die Chris Haumesser
2004-11-11 9:14 ` Sune Kloppenborg Jeppesen
2004-11-11 10:56 ` [gentoo-security] The solution and hopefully the end Paul de Vrieze
2004-11-10 5:00 ` [gentoo-security] Re: Out of air Jason Stubbs
2004-11-10 12:54 ` Antoine Martin
2004-11-10 12:46 ` Rui Pedro Figueira Covelo
2004-11-10 13:10 ` Antoine Martin
2004-11-10 12:55 ` Klaus Wagner
2004-11-10 13:15 ` Andreas Waschbuesch
2004-11-10 13:26 ` Antoine Martin
2004-11-10 13:31 ` Anthony Metcalf
2004-11-10 14:03 ` Antoine Martin
2004-11-10 13:55 ` Anthony Metcalf
2004-11-10 14:04 ` Calum
-- strict thread matches above, loose matches on Subject: below --
2004-11-10 1:21 [gentoo-security] Out of air (was: Let's blow the whistle) Peter Simons
2004-11-10 2:25 ` [gentoo-security] Out of air RNuno
2004-11-10 3:07 ` [gentoo-security] " Peter Simons
2004-11-10 3:10 ` Anthony Gorecki
2004-11-10 3:29 ` Marius Mauch
[not found] ` <4191882C.3010002@ca.istop.com>
[not found] ` <87zn1qtmd2.fsf@peti.cryp.to>
2004-11-10 3:31 ` Den
2004-11-10 3:41 ` Peter Simons
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=41919EC1.5010809@awry.ws \
--to=ch@awry.ws \
--cc=gentoo-security@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