public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [News item review] Portage rsync tree verification
Date: Thu, 25 Jan 2018 11:04:27 +0100	[thread overview]
Message-ID: <1516874667.1833.4.camel@gentoo.org> (raw)

Hi,

This one would be committed once new sys-apps/portage release is wrapped
up and hits ~arch.

---
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

Starting with sys-apps/portage-2.3.22, Portage enables strong
cryptographic verification of the Gentoo rsync tree by default.
This aims to prevent malicious third parties from altering the contents
of the ebuild repository received by our users.

The verification is implemented using app-portage/gemato. Currently,
the whole repository is verified after syncing. On systems with slow
hard drives, this could take around 2 minutes. If you wish to disable
it, you can disable the 'rsync-verify' flag on sys-apps/portage
or set 'sync-rsync-verify-metamanifest = no' in your repos.conf.

Please note that the verification currently does not prevent Portage
from using the repository after syncing. If 'emerge --sync' fails,
do not install any packages and retry syncing. In case of prolonged
or frequent verification failures, please make sure to report a bug
including the failing mirror addresses (found in emerge.log).

The verification uses keys provided by the app-crypt/gentoo-keys
package. The keys are refreshed from the keyserver before every use
in order to check for revocation. The post-sync verification ensures
that the key package is verified itself. However, manual verification
is required before the first use.

On new Gentoo installations including portage-2.3.22, the verification
of the keys will be covered by verifying the installation media
and repository snapshot signatures. On existing installations, you need
to manually compare the primary key fingerprint (reported by gemato
on every sync) against the official Gentoo keys [1]. An example gemato
output is:

  INFO:root:Valid OpenPGP signature found:
  INFO:root:- primary key: 1234567890ABCDEF1234567890ABCDEF12345678
  INFO:root:- subkey: FEDCBA0987654321FEDCBA0987654321FEDCBA09

The primary key printed must match 'Gentoo Portage Snapshot Signing Key'
on the site. Please make sure to also check the certificate used
for the secure connection to the site!

[1]:https://www.gentoo.org/downloads/signatures/
---

-- 
Best regards,
Michał Górny



             reply	other threads:[~2018-01-25 10:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 10:04 Michał Górny [this message]
2018-01-25 10:52 ` [gentoo-dev] Re: [News item review] Portage rsync tree verification 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
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=1516874667.1833.4.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --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