public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] digest-* files in portage tree
Date: Thu, 24 Mar 2005 09:37:55 -0500	[thread overview]
Message-ID: <200503240937.55173.vapier@gentoo.org> (raw)
In-Reply-To: <4242CBD5.8030203@pnpitalia.it>

On Thursday 24 March 2005 09:16 am, Francesco Riosa wrote:
> Chris Gianelloni ha scritto:
> >On Thu, 2005-03-24 at 14:22 +0100, Francesco Riosa wrote:
> >>In addition to "Manifest" files in portage tree there are 19000
> >>"digest-${P}" files in the portage tree each of this uses 4k on ext{2,3}
> >>filesystem and has to be scanned each time rsync is run on the tree.
> >>Is possible to avoid the use of theese files?
> >
> >Not if you ever want to ensure that what you're downloading hasn't been
> >trojaned or otherwise tampered with.
>
> ok, this is true only when you have FEATURES="strict" or "cvs" that it's
> not the default.

no it's not

Manifest is checked when you have FEATURES=strict, digest is checked everytime 
you fetch/unpack files ... all those little 'src_uri md5' lines is a check 
against the digest
-mike
--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-03-24 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 13:22 [gentoo-dev] digest-* files in portage tree Francesco Riosa
2005-03-24 13:36 ` Chris Gianelloni
2005-03-24 14:16   ` Francesco Riosa
2005-03-24 14:37     ` Mike Frysinger [this message]
2005-03-24 15:45       ` Francesco Riosa
2005-03-24 15:42 ` Aron Griffis
2005-03-25  1:46   ` Marius Mauch
2005-03-25  4:28     ` Daniel
2005-03-27  3:31       ` Daniel
2005-03-26  7:43     ` Peter Cech
2005-03-25  6:04 ` Daniel Goller
2005-03-25  7:12   ` Robin H. Johnson
2005-03-25 23:55     ` [gentoo-dev] " Duncan

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=200503240937.55173.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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