From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [News item review] Portage rsync tree verification (v2)
Date: Thu, 25 Jan 2018 22:21:04 +0000 [thread overview]
Message-ID: <robbat2-20180125T221502-520102938Z@orbis-terrarum.net> (raw)
In-Reply-To: <CAOazyz2T2DK1Z1XeNUnQxEVYpfmsBUX=8zP1XfVEe_tgHJ+Yug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
On Thu, Jan 25, 2018 at 11:55:58PM +0200, Alon Bar-Lev wrote:
> I did not looked into the detailed implementation, however, please
> make sure integrity check handles the same cases we have applied to
> emerge-webrsync in the past, including:
Gemato is the implementation of GLEP74/MetaManifest, which DOES
explicitly address both of these concerns.
> 1. Fast forward only in time, this is required to avoid hacker to
> redirect into older portage to install vulnerabilities that were
> approved at that time.
Replay attacks per #1 are addressed via TIMESTAMP field in MetaManifest.
> 2. Content integrity, especially removal, as far as I understand, the
> mechanism will not enable to detect authorized removal of content.
I think you meant 'unauthorized' rather than 'authorized' here.
It will detect files that are expected to exist but are missing.
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]
next prev parent reply other threads:[~2018-01-25 22:21 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
2018-01-25 21:55 ` Alon Bar-Lev
2018-01-25 22:21 ` Robin H. Johnson [this message]
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=robbat2-20180125T221502-520102938Z@orbis-terrarum.net \
--to=robbat2@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