From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --sync
Date: Mon, 01 Aug 2022 11:08:08 +0100 [thread overview]
Message-ID: <4205535.ejJDZkT8p0@lenovo.localdomain> (raw)
In-Reply-To: <20220801114355.266ba10c@ventiloplattform.tastytea.de>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Monday, 1 August 2022 10:43:55 BST tastytea wrote:
> On 2022-08-01 07:58+0100 Michael <confabulate@kintzios.com> wrote:
> > […]
> >
> > 2. These days rsync uses hashes and gpg to check the integrity of
> > portage and will flag up a warning in case of file tampering, or
> > corrupt data. As far as I know such a solution doesn't exist with
> > git.
>
> Verification can be turned on with
> sync-git-verify-commit-signature = yes
> in repos.conf.[1] This does not seem to be enabled by default.[2]
>
> [1]
> <https://wiki.gentoo.org/wiki/Project:Portage/Repository_verification#git>
> [2] <https://wiki.gentoo.org/wiki/Portage_Security#git-mirror_repositories>
I see ... this is an improvement from what I recall it to be. Thanks for
pointing it out. Perhaps I should start using git again. :-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-01 10:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 19:51 [gentoo-user] --sync n952162
2022-07-31 20:24 ` Jack
2022-07-31 20:32 ` Dale
2022-07-31 20:43 ` Neil Bothwick
2022-07-31 23:49 ` Peter Humphrey
2022-08-01 0:21 ` Lee
2022-08-02 16:28 ` [ME TOO] " Dr Rainer Woitok
2022-07-31 20:53 ` Stefan Schmiedl
2022-07-31 22:55 ` Lee
2022-07-31 23:21 ` Neil Bothwick
2022-08-01 5:09 ` n952162
2022-08-01 6:58 ` Michael
2022-08-01 7:22 ` Neil Bothwick
2022-08-01 9:43 ` tastytea
2022-08-01 10:08 ` Michael [this message]
2022-08-02 13:22 ` [gentoo-user] --sync Grant Edwards
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=4205535.ejJDZkT8p0@lenovo.localdomain \
--to=confabulate@kintzios.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