all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Yet another Hydra mirror: hydra-mirror.marusich.info
Date: Wed, 09 Mar 2016 13:37:47 +0100	[thread overview]
Message-ID: <87twkfesis.fsf@gnu.org> (raw)
In-Reply-To: <20160308095733.GA15199@solar> (Andreas Enge's message of "Tue, 8 Mar 2016 10:57:33 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> On Tue, Mar 08, 2016 at 10:04:33AM +0100, Andy Wingo wrote:
>> Right now hydra.gnu.org is in this weird situation where people who use
>> it have to trust it, modulo "guix challenge" of course.  But really all
>> we have to trust is the mapping from the derivation (like the "foo"
>> package) to a hash of the build results; the actual build result could
>> be transferred from anywhere with no trust issues at all, provided that
>> we verify the hash.  (Do I understand the situation correctly?)
>
> Yes, if I understand you correctly :-)

I think you both understand correctly.  :-)

That is, hydra.gnu.org serves narinfos like:

  http://hydra.gnu.org/n0rgvy9c0cwv453k5bczwscp6iwqa4fc.narinfo

They contain all the meta-data for the corresponding store item,
including a hash of its content, and said meta-data is signed.  See
(guix pki) and
<https://www.gnu.org/software/guix/manual/html_node/Substitutes.html>
for details

This is why we can mirror things as-is and have users benefit from it
without having to trust any additional party.


Mirrors are nice because they’re easy to set up, completely transparent
for users, and allow our infrastructure to scale quickly.  Now, another
thing that would be great is to have independent build farms (running
‘guix publish’) so there is no single point of trust.

Ludo’.

  reply	other threads:[~2016-03-09 12:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  6:37 Yet another Hydra mirror: hydra-mirror.marusich.info Chris Marusich
2016-03-08  9:04 ` Andy Wingo
2016-03-08  9:57   ` Andreas Enge
2016-03-09 12:37     ` Ludovic Courtès [this message]
2016-03-08  9:13 ` Ludovic Courtès
2016-03-09  8:27   ` Chris Marusich
2016-03-09 12:42     ` Ludovic Courtès
2016-03-11  4:08       ` Chris Marusich
2016-03-11 14:47         ` Ludovic Courtès
2016-04-06 13:43 ` Nils Gillmann
2016-04-07  4:56   ` Chris Marusich

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=87twkfesis.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.