From: ludo@gnu.org (Ludovic Courtès)
To: Christian Grothoff <christian@grothoff.org>
Cc: guix-devel@gnu.org, gnunet-developers@gnu.org
Subject: Re: [GSoC] GNUnet binary distribution system
Date: Mon, 10 Mar 2014 23:26:37 +0100 [thread overview]
Message-ID: <87eh29itb6.fsf@gnu.org> (raw)
In-Reply-To: <531E3695.9010605@grothoff.org> (Christian Grothoff's message of "Mon, 10 Mar 2014 23:03:01 +0100")
Christian Grothoff <christian@grothoff.org> skribis:
> On 03/10/2014 10:09 PM, Ludovic Courtès wrote:
>> The initial discussion [0] left open the question of where binaries
>> themselves should be stored. A possibility would be to use GNUnet’s
>> DHT simply as a discovery mechanism, and then to establish a
>> connection directly to the user’s machine, which would run, say, and
>> HTTP server.
>
> I'd ACK using the DHT, but the use of HTTP means that it (often) won't
> work if the peer is behind NAT. If you instead use GNUnet MESH to
> establish a TCP-like connection to the file transfer, you might be
> less efficient than a direct TCP/HTTP connection, but you should get
> through NAT _and_ be less observable _and_ have "good" encryption
> (not just TLS).
Makes a lot of sense, indeed.
Thanks, that’s the kind of input I was expecting. :-)
Ludo’.
_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers
next prev parent reply other threads:[~2014-03-10 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 18:41 [GSoC] GNUnet binary distribution system Pierre-Antoine Rault
2014-03-10 21:09 ` Ludovic Courtès
2014-03-10 22:03 ` Christian Grothoff
2014-03-10 22:26 ` Ludovic Courtès [this message]
2014-03-10 23:19 ` Pierre-Antoine Rault
2014-03-11 3:35 ` Mark H Weaver
2014-03-11 6:59 ` Pierre-Antoine Rault
2014-03-11 18:29 ` Mark H Weaver
2014-03-11 8:42 ` Christian Grothoff
2014-03-11 13:06 ` 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=87eh29itb6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=christian@grothoff.org \
--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.