From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: All sorts of digest verification failures
Date: Mon, 16 Nov 2015 22:49:32 +0100 [thread overview]
Message-ID: <2115081.hdzugRMeM0@thetick> (raw)
In-Reply-To: <n2d3a3$sbg$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Monday 16 November 2015 17:21:07 Martin Vaeth wrote:
>covici@ccs.covici.com <covici@ccs.covici.com> wrote:
>> I have thinmanifests=true as specified in some news item or post, I
>> think this was a mandatory change some time ago using rsync.
>
>If you really use rsync/webrsync and not git, this is unlikely:
>The file containing this line (metadata/layout.conf) should be
>overridden at every rsync (unless you took special measures,
>but this was certainly never recommended).
>
>> They figured the ebuilds sync anyway so no reason for the
>> manifests to have them.
>
>It is not about syncing but about security (checksums with
>signatures should safe you from MITM and even compromised
>servers). Thin-manifests was only meant for git, because git
>already contains checksums ('though only less secure sha1,
>but that's a different story), so it was decided that no
>duplicate checksums are needed for git.
>For *rsync* the situation is different.
Don't forget that in Gentoo all commits are also GPG signed.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-16 21:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 16:07 [gentoo-user] All sorts of digest verification failures Grant Edwards
2015-11-12 16:19 ` wabenbau
2015-11-12 16:42 ` [gentoo-user] " Grant Edwards
2015-11-12 16:45 ` Alan McKinnon
2015-11-12 16:54 ` Peter Humphrey
2015-11-15 9:59 ` Alan Mackenzie
2015-11-15 10:22 ` Matti Nykyri
2015-11-15 10:43 ` Peter Humphrey
2015-11-15 10:56 ` Matti Nykyri
2015-11-15 11:44 ` Peter Humphrey
2015-11-15 11:01 ` Alan Mackenzie
2015-11-15 11:15 ` Matti Nykyri
2015-11-15 19:33 ` Alan Mackenzie
2015-11-15 21:43 ` Matti Nykyri
2015-11-15 10:41 ` Neil Bothwick
2015-11-15 11:42 ` Neil Bothwick
2015-11-15 14:56 ` Martin Vaeth
2015-11-15 17:17 ` Neil Bothwick
2015-11-15 19:05 ` Martin Vaeth
2015-11-15 20:19 ` Dale
2015-11-15 20:29 ` covici
2015-11-15 21:02 ` Simon Thelen
2015-11-16 6:45 ` Martin Vaeth
2015-11-16 7:33 ` covici
2015-11-16 17:21 ` Martin Vaeth
2015-11-16 21:49 ` Marc Joliet [this message]
2015-11-16 22:32 ` Rich Freeman
2015-11-17 7:09 ` Marc Joliet
2015-11-15 20:43 ` Grant Edwards
2015-11-16 8:51 ` Dale
2015-11-16 1:39 ` walt
2015-11-16 9:33 ` Neil Bothwick
2015-11-16 9:48 ` Dale
2015-11-16 13:53 ` Neil Bothwick
2015-11-15 19:29 ` Alan Mackenzie
2015-11-12 16:59 ` Dale
2015-11-12 16:33 ` [gentoo-user] " Dale
2015-11-16 0:06 ` Dale
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=2115081.hdzugRMeM0@thetick \
--to=marcec@gmx.de \
--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