all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: amirouche <amirouche@hypermove.net>
Cc: guix-devel@gnu.org, gnunet-developers@gnu.org
Subject: Re: gnunet-guile reboot & guix (take two)
Date: Mon, 05 Feb 2018 14:25:50 +0100	[thread overview]
Message-ID: <871shzd0v5.fsf@gnu.org> (raw)
In-Reply-To: <1517663436.2217.0@mail.gandi.net> (amirouche@hypermove.net's message of "Sat, 03 Feb 2018 14:10:36 +0100")

Hi amirouche,

amirouche <amirouche@hypermove.net> skribis:

> After discussing gnunet & guix at fosdem with gnunet
> people I have better picture of where things can go.
>
> The short story is:
>
> 1) There is no way to know the gnunet hash aka. gnunet uri
>   of a substitute before the build.
>
> 2) There is no way to associate gnunet hash and guix hash
>   in a secure/trusted manner over gnunet. Except maybe
>   if we use GNS to publish guix hash as subdomains of
>   substitute-server.guix.gnu?

Before jumping to conclusions, did you check the narinfo format that we
use on HTTP?  A narinfo is essentially a statement that a given store
item, resulting from a .drv build, has a specific content hash.

Lookup by content hash over GNUnet’s AFS is all we’d need.

See also the discussion in
<https://www.gnu.org/software/guix/blog/2017/reproducible-builds-a-status-update/>.

HTH!

Ludo’.

_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers

  parent reply	other threads:[~2018-02-05 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 13:10 gnunet-guile reboot & guix (take two) amirouche
2018-02-03 14:46 ` Adam Van Ymeren
2018-02-05 13:25 ` Ludovic Courtès [this message]
2018-02-05 18:51   ` Ricardo Wurmus
2018-02-09 15:27 ` [GNUnet-developers] " amirouche

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=871shzd0v5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=amirouche@hypermove.net \
    --cc=gnunet-developers@gnu.org \
    --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.