From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage + checksums
Date: Tue, 6 Apr 2010 16:13:47 -0500 [thread overview]
Message-ID: <i2z58965d8a1004061413xff01aec8r4f99b1a7487c3d5b@mail.gmail.com> (raw)
In-Reply-To: <201004062241.18305.alan.mckinnon@gmail.com>
On Tue, Apr 6, 2010 at 3:41 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Tuesday 06 April 2010 20:56:30 Butterworth, John W. wrote:
>> Thanks.
>>
>> Do you know if someone makes a change to a copy of apache hosted on a
>> public mirror, will the sync between the servers determine that it's
>> corrupted (via 'bad' checksum) on the public side and replace it?
>
> I can answer this, I run a public Gentoo mirror (not an official one)
>
> If I, or some clown, loads a trojaned copy of Apache source code into
> my distfiles mirror, portage will complain bitterly because the hash in the
> manifest will fail. Then you will know something is wrong.
>
> If I trojan the ebuild and the portage tree to match my trojaned sources, you
> will probably not pick it up. This would be very risky indeed for me to do as
> I can't be sure you will sync the tree and get your distfiles from me.
Isn't there something like FEATURES="gpg" to enable checking gpg
signatures on ebuilds? (I haven't tried it so I don't know if this is
actually used)
next prev parent reply other threads:[~2010-04-06 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 18:15 [gentoo-user] Portage + checksums Butterworth, John W.
2010-04-06 18:24 ` Albert W. Hopkins
2010-04-06 18:56 ` Butterworth, John W.
2010-04-06 20:10 ` Jonas de Buhr
2010-04-06 20:41 ` Alan McKinnon
2010-04-06 21:13 ` Paul Hartman [this message]
2010-04-06 21:26 ` Alan McKinnon
2010-04-06 21:46 ` Mark Knecht
2010-04-06 22:16 ` Alan McKinnon
2010-04-07 5:58 ` Mick
2010-04-07 12:35 ` Jonas de Buhr
2010-04-07 15:06 ` Butterworth, John W.
2010-04-08 22:58 ` Mick
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=i2z58965d8a1004061413xff01aec8r4f99b1a7487c3d5b@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@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