From: Jonas de Buhr <jonas.de.buhr@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage + checksums
Date: Tue, 6 Apr 2010 22:10:17 +0200 [thread overview]
Message-ID: <20100406221017.78fc1676@toxic.dbnet> (raw)
In-Reply-To: <8622C222D2FC9D499533B1EEF631D3930332DB4A6F@IMCMBX1.MITRE.ORG>
Hi!
>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'm not sure how gentoo mirrors do the syncing but in a lot of cases an
error like this would show up on the downloading (client-/mirror-) side
which wont help you at all if you don't trust the mirror.
The way I undestand this a problem is that any mirror may simply
regenerate hash values like RMD160 or SHA1 for modified sourcefiles. If
you don't compare them to those from a trusted server you will never
know.
So a general aproach to this may be that some gentoo core team would
sign everything with one (or a set of) private key(s) of some kind and
publish the corresponding public key(s) on their website and with the
install images. The signature could easily be copied to mirrors but not
regenerated for changed sourcefiles.
However that would be a lot more work for the gentoo developers since
*few* (else it's pointless) trusted people with access to the private
key would have to approve every single update for every arch and
compare every source tarball to a trusted one.
Maybe you could run your own mirror and sync it to a trusted one?
Bye,
jdb
next prev parent reply other threads:[~2010-04-06 20:13 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 [this message]
2010-04-06 20:41 ` Alan McKinnon
2010-04-06 21:13 ` Paul Hartman
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=20100406221017.78fc1676@toxic.dbnet \
--to=jonas.de.buhr@gmx.net \
--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