From: "Hanno Böck" <hanno@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] GLEP 74: Full-tree verification using Manifest files
Date: Fri, 27 Oct 2017 23:48:04 +0200 [thread overview]
Message-ID: <20171027234804.535f6e13@pc1> (raw)
In-Reply-To: <1509048745.18656.6.camel@gentoo.org>
Hi,
On Thu, 26 Oct 2017 22:12:25 +0200
Michał Górny <mgorny@gentoo.org> wrote:
> After a week of hard work, I'd like to request your comments
> on the draft of GLEP 74. This GLEP aims to replace the old
> tree-signing GLEPs 58 and 60 with a superior implementation and more
> complete specification.
Thanks for working on this, it's really one of the biggest security
issues Gentoo has these days that need to be fixed.
I hope I'll find time to read it in detail, but by skimming through it
I noted that the downgrade attack prevention is kinda not very clear.
It says in the timestamp section "The package manager can use it to
detect an outdated repository checkout." But it doesn't say how exactly.
Should a package manager reject a sync if it is too old? or not install
packages if a sync hasn't happened for some time? What is considered
"outdated"? I think that should be clarified how exactly it's supposed
to work.
--
Hanno Böck
https://hboeck.de/
mail/jabber: hanno@hboeck.de
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42
next prev parent reply other threads:[~2017-10-27 21:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 20:12 [gentoo-dev] [RFC] GLEP 74: Full-tree verification using Manifest files Michał Górny
2017-10-26 21:58 ` Roy Bamford
2017-10-27 6:22 ` Michał Górny
2017-10-28 2:41 ` Dean Stephens
2017-10-27 21:05 ` Robin H. Johnson
2017-10-28 11:50 ` Michał Górny
2017-10-28 12:49 ` Ulrich Mueller
2017-10-28 13:23 ` Michał Górny
2017-10-28 13:46 ` Ulrich Mueller
2017-10-28 20:55 ` Michał Górny
2017-10-28 18:44 ` Robin H. Johnson
2017-10-29 18:47 ` Michał Górny
2017-10-29 20:54 ` Robin H. Johnson
2017-10-30 16:01 ` Michał Górny
2017-10-27 21:48 ` Hanno Böck [this message]
2017-10-28 2:41 ` Dean Stephens
2017-10-28 3:27 ` M. J. Everitt
2017-10-28 4:43 ` Allan Wegan
2017-10-29 19:07 ` [gentoo-dev] [v1.0.1] " Michał Górny
2017-10-29 20:39 ` Robin H. Johnson
2017-10-30 16:11 ` Michał Górny
2017-10-30 16:51 ` [gentoo-dev] [v1.0.2] " Michał Górny
2017-10-30 19:56 ` Robin H. Johnson
2017-11-01 8:44 ` Michał Górny
2017-11-01 9:47 ` Walter Dnes
2017-11-01 13:08 ` Andreas K. Huettel
2017-11-02 19:10 ` Michał Górny
2017-11-02 19:11 ` [gentoo-dev] [v1.0.3] " Michał Górny
2017-11-02 23:43 ` Robin H. Johnson
2017-11-05 21:10 ` Michał Górny
2017-11-06 20:42 ` Robin H. Johnson
2017-11-06 21:53 ` [gentoo-dev] [v1.0.4] " 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=20171027234804.535f6e13@pc1 \
--to=hanno@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