all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Rémi Birot-Delrue" <asgeir@free.fr>
Cc: guix-devel@gnu.org, gnunet-developers@gnu.org
Subject: Re: [GSoC] Guix + GNUnet: what’s next
Date: Thu, 02 Jul 2015 22:32:25 +0200	[thread overview]
Message-ID: <87mvzewbae.fsf@gnu.org> (raw)
In-Reply-To: <87si9633p7.fsf@free.fr> ("Rémi Birot-Delrue"'s message of "Thu, 02 Jul 2015 18:49:08 +0200")

(Sorry, I had misspelled the GNUnet mailing list address.)

Rémi Birot-Delrue <asgeir@free.fr> skribis:

> Ludovic Courtès writes:
>
>> I’m not completely clear on how search for substitutes will work,
>> though.  Currently, when the user wants to build /gnu/store/xyz, ‘guix
>> substitute’ simply fetches http://hydra.gnu.org/xyz.narinfo.  How will
>> that work with GNUnet?  Are we going to look up their /gnu/store file
>> name?
>
> I’ve considered a solution for that: GNUnet allows one to create
> specific namespace and publish files under this namespace. Unlike
> publishing under the “global namespace” where keywords are used to
> identify a file, when publishing under a specific namespace files are
> identified with a choosen identifier. Moreover, as a namespace is
> basically a cryptographic key pair, and publishing a file under your
> namespace means signing, one’s assured nobody else will publish under
> her or his namespace. By the way, the private key associated with a
> namespace is named “ego” or “pseudonym”.
>
> It’s easy to test this feature:
>
>     # create a `test` ego/namespace
>     $ gnunet-identity -C test
>
>     # list the known egos in the form: `name - public key`
>     $ gnunet-identity -d
>     test - M2OC987U9LFJHQ8LC9SLCV4Q0ONHJV7FMTFQ2VRPE0M9R9MK5860
>     …
>
>     # index the file `foo.txt` under the `test` namespace
>     $ gnunet-publish -P test -t foobarbaz foo.txt
>
>     # find the file `foo.txt`
>     $ gnunet-search gnunet://fs/sks/M2OC987U9LFJHQ8LC9SLCV4…/foobarbaz
>     #0:
>     gnunet-download -o "foo.txt" gnunet://fs/chk/PL217ODD8EDSMOIQ3UT0…
>
> Now if Alice wants to publish her binaries, she creates an ego/namespace
> and publishes everything under it; Bob adds her namespace’s public key
> to his authorized substitutes list, and when installing `/gnu/store/xyz`
> the substitute will search for `gnunet://fs/sks/<Alice’s key>/xyz`.
>
> Instead of publishing an archive we might also directly publish/index
> the build, but I don’t know if it’s viable.
>
> Does it seem right to you?

Sounds good!  I wasn’t use whether the ID passed to ‘gnunet-publish -t’
could be used as a key to look up the data, but that seems to be the
case.

Thanks,
Ludo’.

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

  reply	other threads:[~2015-07-02 20:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 11:15 [GSoC] Guix + GNUnet: what’s next Rémi Birot-Delrue
2015-07-02 12:33 ` Ludovic Courtès
2015-07-02 16:49   ` Rémi Birot-Delrue
2015-07-02 20:32     ` Ludovic Courtès [this message]
2015-07-02 21:58       ` [OSM-dev] [GNUnet-developers] " Daniel Golle
2015-07-02 22:56         ` Paul Norman
2015-07-03  2:02           ` [OSM-dev] " Daniel Golle

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=87mvzewbae.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=asgeir@free.fr \
    --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.