public inbox for gentoo-security@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Frey <cdfrey@netdirect.ca>
To: gentoo-security@lists.gentoo.org
Subject: [gentoo-security] Re: Is anybody else worried about this?   (was: Trojan for Gentoo, part 2)
Date: Sun, 7 Nov 2004 12:01:35 -0500	[thread overview]
Message-ID: <20041107120135.C9045@netdirect.ca> (raw)
In-Reply-To: <20041107154046.GG10927@mail.lieber.org>; from klieber@gentoo.org on Sun, Nov 07, 2004 at 03:40:46PM +0000

On Sun, Nov 07, 2004 at 03:40:46PM +0000, Kurt Lieber wrote:
> As another poster already noted, of course it is, but it's not specific to
> Gentoo.  What happens if the server hosting the master repository of glibc
> gets compromised?  How do you know that hasn't already happened and there's
> back doors galore on your machine right now?  That may seem like a
> smart-ass question, but stop for a moment and consider it seriously.  How
> do you *KNOW* that there are no backdoors in the version of glibc on your
> computer right now?  

You don't.  But that's like saying there's no point in closing the front
door since the bedroom window might be open.  If the front door is closed
and locked, then at least we can pay more attention to the open window.

Plus, the glibc ebuild maintainer should be tracking the changes.  He knows
what's going on in glibc land, he knows the build process, he should be
in touch with the main developers, and he should be reading the diffs.

If he doesn't have the time or skill to do that, he can at least compare
against the work of people who do, such as the source packages of Debian
or Fedora Core.  It is pretty easy to do a diff.

Plus #2: both the glibc tarballs and the source packages of other distros
are signed.  The glibc maintainer should have all those signatures on hand,
if needed, and be verifying them all before he puts the entire Gentoo
user base at risk.

I think this point is a red herring.

> >  (2) Are there plans for getting it fixed?
> 
> We already implemented a major change nearly a year ago by moving
> 'rsync.gentoo.org' onto servers that are managed by the Gentoo team.
> Previously, we relied on community mirrors which worked well, but didn't
> allow us to ensure the servers were all held to the same high security
> standard. 

Excellent.

> We've also taken a number of other steps to mitigate this type of exposure
> including getting GPG signing into portage and the creation of an auditing
> project which reviews the ebuilds and code used in our distribution.

Fantastic.

> > I have read some of the material Alexander hyper-linked to
> > and, frankly, most of it is outright frightening.
> 
> Then you should immediately unplug your computer from the internet.  The
> minute you jack in, you're accepting some level of risk.  That's just the
> nature of the beast.

That's rather condescending.

I would instead recommend that he compare Gentoo to other distros that take
package signing more seriously.  It may be that the features and benefits
of a source-based distro like Gentoo outweigh the need for signed ebuilds,
like it does for me on one of my machines.  But it also may mean that
some machines require the security and peace of mind of another distro's
signing practices and verification policies.  Other machines I admin
fall into this category as well.

- Chris


--
gentoo-security@gentoo.org mailing list


  reply	other threads:[~2004-11-07 17:01 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 20:16 [gentoo-security] Trojan for Gentoo, part 2 Alexander Holler
2004-11-07  0:31 ` [gentoo-security] " Chris Frey
2004-11-07 13:10   ` [gentoo-security] help blocking automated ssh scanning attack script Brian G. Peterson
2004-11-07 13:16     ` Gary Nichols
2004-11-07 13:31       ` Brian G. Peterson
2004-11-07 13:37     ` Rui Covelo
2004-11-07 13:50     ` aScii
2004-11-08  4:44       ` Kim Nielsen
2004-11-07 14:50   ` [gentoo-security] Re: Trojan for Gentoo, part 2 Jason Rojas
2004-11-07 17:01     ` Carsten Lohrke
2004-11-07 15:23   ` Kurt Lieber
2004-11-07 15:44     ` Peter Simons
2004-11-07 15:49       ` Kurt Lieber
2004-11-07 16:01         ` Jan Groenewald
2004-11-07 16:07         ` Peter Simons
2004-11-07 16:52           ` Dan Margolis
2004-11-07 17:43             ` Andreas Waschbuesch
2004-11-07 17:52               ` Dan Margolis
2004-11-07 19:08                 ` Chocron J.
2004-11-07 19:11                 ` Andreas Waschbuesch
2004-11-08  2:41       ` [gentoo-security] How to authenticate the portage tree Peter Simons
2004-11-08  9:37         ` [gentoo-security] Gentoo Portage Attack Tree Ervin Németh
2004-11-08 10:11           ` Kurt Lieber
2004-11-08 12:15           ` [gentoo-security] " Peter Simons
2004-11-12  7:00             ` Ed Grimm
2004-11-08 20:05         ` [gentoo-security] How to authenticate the portage tree Marius Mauch
2004-11-07 13:14 ` [gentoo-security] Is anybody else worried about this? (was: Trojan for Gentoo, part 2) Peter Simons
2004-11-07 15:40   ` [gentoo-security] Is anybody else worried about this? Marc Ballarin
2004-11-07 15:15     ` Tobias Klausmann
2004-11-07 15:20     ` Alex
2004-11-07 15:28     ` [gentoo-security] " Peter Simons
2004-11-07 15:45       ` Rui Covelo
2004-11-07 16:44         ` [gentoo-security] " Chris Frey
2004-11-07 17:04           ` Rui Covelo
2004-11-07 17:11             ` [gentoo-security] " Chris Frey
2004-11-07 17:56             ` [gentoo-security] " Peter Simons
2004-11-07 18:00       ` Marc Ballarin
2004-11-07 17:26         ` Barry.Schwartz
2004-11-07 16:31     ` Chris Frey
2004-11-07 17:07     ` [gentoo-security] " Dan Margolis
     [not found]     ` <418E5425.6070400@seas.upenn.edu>
2004-11-07 18:34       ` Marc Ballarin
2004-11-07 17:57         ` Dan Margolis
2004-11-07 19:36           ` Marc Ballarin
2004-11-07 18:51             ` [gentoo-security] " Peter Simons
2004-11-08 20:12               ` Marius Mauch
2004-11-07 15:40   ` [gentoo-security] Is anybody else worried about this? (was: Trojan for Gentoo, part 2) Kurt Lieber
2004-11-07 17:01     ` Chris Frey [this message]
2004-11-07 18:35       ` [gentoo-security] " Dan Noe
2004-11-07 19:04       ` Marc Ballarin
2004-11-07 18:25         ` Peter Simons
2004-11-07 23:26       ` Kurt Lieber
2004-11-07 23:52         ` [gentoo-security] No, apparently not. (was: Is anybody else worried about this?) Peter Simons
2004-11-08  0:17           ` Kurt Lieber
2004-11-08  1:05             ` [gentoo-security] " Peter Simons
2004-11-08  1:08               ` Anthony Gorecki
2004-11-08  1:18                 ` Peter Simons
2004-11-08 16:11                   ` Jake Hawkes
2004-11-08  1:31               ` Kurt Lieber
2004-11-08  1:35                 ` Peter Simons
2004-11-08  9:19                 ` Tobias Klausmann
2004-11-08 10:19                   ` Kurt Lieber
2004-11-08 11:53                     ` Tobias Klausmann
2004-11-08 12:17                       ` Anthony Metcalf
2004-11-08 10:30                   ` [gentoo-security] Re: No, apparently not Thierry Carrez
2004-11-08 12:01                     ` Peter Simons
2004-11-08 10:36                   ` [gentoo-security] Keys on a cd? Anthony Metcalf
2004-11-08 13:30                     ` Kurt Lieber
2004-11-08  2:17           ` [gentoo-security] No, apparently not Brian Bilbrey
2004-11-08  2:33             ` [gentoo-security] " Peter Simons
2004-11-08  2:49             ` [gentoo-security] " Ed Grimm
2004-11-08  2:51               ` [gentoo-security] " Peter Simons
2004-11-08  3:01                 ` Ed Grimm
2004-11-08  3:08                   ` Peter Simons
2004-11-08  1:03         ` [gentoo-security] Re: Re: Is anybody else worried about this? (was: Trojan for Gentoo, part 2) Chris Frey
2004-11-08  1:19           ` Kurt Lieber

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=20041107120135.C9045@netdirect.ca \
    --to=cdfrey@netdirect.ca \
    --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