From: R0b0t1 <r030t1@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [News item review] Portage rsync tree verification (v2)
Date: Sun, 28 Jan 2018 00:40:17 -0600 [thread overview]
Message-ID: <CAAD4mYhooRycHD0f44ot7gfAgbXooJfw=WtS1z4n7Tz4dOviKA@mail.gmail.com> (raw)
In-Reply-To: <1517063245.3816.13.camel@gentoo.org>
On Sat, Jan 27, 2018 at 8:27 AM, Michał Górny <mgorny@gentoo.org> wrote:
> W dniu czw, 25.01.2018 o godzinie 15∶55 -0600, użytkownik R0b0t1
> napisał:
>> On Thu, Jan 25, 2018 at 3:45 PM, Michał Górny <mgorny@gentoo.org> wrote:
>> > W dniu czw, 25.01.2018 o godzinie 21∶37 +0000, użytkownik Robin H.
>> > Johnson napisał:
>> > > On Thu, Jan 25, 2018 at 01:35:17PM +0100, Michał Górny wrote:
>> > > > Title: Portage rsync tree verification
>> > > > Author: Michał Górny <mgorny@gentoo.org>
>> > > > Posted: 2018-01-xx
>> > > > Revision: 1
>> > > > News-Item-Format: 2.0
>> > > > Display-If-Installed: <sys-apps/portage-2.3.21
>> > >
>> > > Drop Display-If-Installed, they need to always see this until they know
>> > > it was bootstrapped.
>> >
>> > Well, the idea was that if someone starts with stage that has >2.3.21,
>> > then he has bootstrapped via verifying the stage signature.
>> >
>> > > > Starting with sys-apps/portage-2.3.22, Portage enables cryptographic
>> > > > verification of the Gentoo rsync repository distributed over rsync
>> > > > by default.
>> > >
>> > > Seems very wordy, suggested cleanup:
>> > > > > Starting with sys-apps/portage-2.3.22, Portage will verify the Gentoo
>> > > > > repository after rsync by default.
>> > > >
>> > > > This aims to prevent malicious third parties from altering
>> > > > the contents of the ebuild repository received by our users.
>> > > >
>> > > > This does not affect users syncing using git and other methods.
>> > > > Appropriate verification mechanisms for them will be provided
>> > > > in the future.
>> > >
>> > > Note that emerge-webrsync has verification via FEATURES=webrsync-gpg?
>> >
>> > I'm sorry, I have never used that. Does it cover full key maintenance
>> > or rely on user to do the gpg work?
>> >
>>
>> It used to be necessary to set up a GnuPG home for portage and pull
>> the keys in, but now users can emerge app-crypt/gentoo-keys and set
>> PORTAGE_GPG_DIR="/var/lib/gentoo/gkeys/keyrings/gentoo/release".
>>
>
> In that case I'd rather not announce it until it is integrated properly.
>
What is "properly?" It's referenced in the handbook.
Cheers,
R0b0t1
next prev parent reply other threads:[~2018-01-28 6:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 10:04 [gentoo-dev] [News item review] Portage rsync tree verification Michał Górny
2018-01-25 10:52 ` [gentoo-dev] " Duncan
2018-01-25 11:01 ` [gentoo-dev] " Kristian Fiskerstrand
2018-01-25 12:30 ` Michał Górny
2018-01-25 21:38 ` M. J. Everitt
2018-01-25 12:35 ` [gentoo-dev] [News item review] Portage rsync tree verification (v2) Michał Górny
2018-01-25 14:49 ` Aaron W. Swenson
2018-01-25 19:13 ` Ulrich Mueller
2018-01-25 21:37 ` Robin H. Johnson
2018-01-25 21:45 ` Michał Górny
2018-01-25 21:55 ` R0b0t1
2018-01-27 14:27 ` Michał Górny
2018-01-28 6:40 ` R0b0t1 [this message]
2018-01-25 21:55 ` Alon Bar-Lev
2018-01-25 22:21 ` Robin H. Johnson
2018-01-25 22:48 ` Alon Bar-Lev
2018-01-27 14:26 ` [gentoo-dev] [News item review] Portage rsync tree verification (v3) Michał Górny
2018-01-27 14:47 ` M. J. Everitt
2018-01-27 15:27 ` [gentoo-dev] " Duncan
2018-01-27 15:50 ` [gentoo-dev] " Nils Freydank
2018-01-28 8:58 ` [gentoo-dev] [News item review] Portage rsync tree verification (v4) Michał Górny
2018-01-28 16:00 ` [gentoo-dev] " Duncan
2018-01-28 20:30 ` [gentoo-dev] " Andrew Barchuk
2018-01-29 7:21 ` Robin H. Johnson
2018-01-29 18:57 ` [gentoo-dev] [News item review] Portage rsync tree verification (v5) Michał Górny
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='CAAD4mYhooRycHD0f44ot7gfAgbXooJfw=WtS1z4n7Tz4dOviKA@mail.gmail.com' \
--to=r030t1@gmail.com \
--cc=gentoo-dev@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