From: ludo@gnu.org (Ludovic Courtès)
To: bancfc@openmailbox.org
Cc: guix-devel@gnu.org, whonix-devel@whonix.org
Subject: Re: GNU Guix Questions
Date: Tue, 07 Mar 2017 14:57:54 +0100 [thread overview]
Message-ID: <87k281chp9.fsf@gnu.org> (raw)
In-Reply-To: <c90c6a2238126ffc507f83180fc4e6a0@openmailbox.org> (bancfc@openmailbox.org's message of "Mon, 06 Mar 2017 16:14:08 +0100")
Hi!
bancfc@openmailbox.org skribis:
> * Does Guix defend against the variety of attacks described in the TUF
> threat model document? (described in link below) How resilient is it
> against key compromise? (TUF was designed from the ground up to
> provide a highly resilient and secure update framework as a drop in
> replacement to crappy standalone updaters - a problem that's become
> very serious for proprietary OSes. The security research and
> implementation behind it are an excellent rubric that one can apply to
> any updater/package manager.)
>
> https://github.com/theupdateframework/tuf/blob/develop/SECURITY.md
The short answer is: not yet.
The longer answer is that TUF is biased towards “traditional” package
managers where the main asset is a binary package archive.
Guix is conceptually a source-based package manager, so what we want to
authenticate is Git checkouts of Guix itself. TUF needs to be “ported”
to this model. We’ll address this hopefully within a few months, and
definitely by 1.0:
https://bugs.gnu.org/22883
Ludo’.
prev parent reply other threads:[~2017-03-07 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 15:14 GNU Guix Questions bancfc
2017-03-06 17:15 ` [Whonix-devel] " ng0
2017-03-07 0:59 ` bancfc
2017-03-07 11:05 ` ng0
2017-03-07 19:31 ` bancfc
2017-03-10 10:44 ` ng0
2017-03-13 22:42 ` bancfc
2017-03-14 13:45 ` Ludovic Courtès
2017-03-07 13:57 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k281chp9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bancfc@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=whonix-devel@whonix.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).