From: ludo@gnu.org (Ludovic Courtès)
To: Sree Harsha Totakura <totakura@in.tum.de>
Cc: gnunet-developers@gnu.org, bug-guix@gnu.org,
Christian Grothoff <grothoff@in.tum.de>
Subject: Re: [GNUnet-developers] Using GNUnet for binary package distribution
Date: Fri, 22 Mar 2013 13:25:36 +0100 [thread overview]
Message-ID: <87r4j7iptr.fsf@gnu.org> (raw)
In-Reply-To: <514B4E16.5040402@in.tum.de> (Sree Harsha Totakura's message of "Thu, 21 Mar 2013 19:14:46 +0100")
Hi,
Sree Harsha Totakura <totakura@in.tum.de> skribis:
> For authentication, we intend to use GPG with gnunet-update. The idea
> is that the gnunet-updater would search for updates using GNUnet's File
> Sharing service and downloads meta-data files. It then verifies if the
> meta-data files are signed by a trusted key (which is user-configurable)
> and proceeds with the download of actual binaries.
OK. Wouldn’t using the AFS service be a bottleneck, in terms of
availability and bandwidth? My impression is that it might be OK for
small updates like those of GNUnet itself, but not for a full distro.
For Guix, downloading binaries is an option that is only worthwhile if
it’s faster than building locally.
Ludo’.
next prev parent reply other threads:[~2013-03-22 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:02 Using GNUnet for binary package distribution Ludovic Courtès
2013-03-21 17:03 ` Andreas Enge
2013-03-21 18:01 ` Christian Grothoff
2013-03-21 18:14 ` Sree Harsha Totakura
2013-03-22 12:25 ` Ludovic Courtès [this message]
2013-03-22 12:57 ` [GNUnet-developers] " Christian Grothoff
2013-03-22 13:56 ` Ludovic Courtès
2013-03-22 12:29 ` [GNUnet-developers] " Ludovic Courtès
[not found] ` <514C6DF0.5000800@in.tum.de>
2013-03-22 14:52 ` Ludovic Courtès
2013-03-23 20:51 ` Sree Harsha Totakura
2013-03-25 10:46 ` Sree Harsha Totakura
2013-03-25 10:51 ` Christian Grothoff
2013-03-25 12:58 ` Ludovic Courtès
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=87r4j7iptr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=gnunet-developers@gnu.org \
--cc=grothoff@in.tum.de \
--cc=totakura@in.tum.de \
/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.