Delivery-Date: Tue, 01 Jul 2014 23:11:59 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 208631E0AB7
	for <archiver@seul.org>; Tue,  1 Jul 2014 23:11:57 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C96282FA9C;
	Wed,  2 Jul 2014 03:11:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A6BDA2EBA3
 for <tor-talk@lists.torproject.org>; Wed,  2 Jul 2014 03:09:30 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id IvcBcYeFB91P for <tor-talk@lists.torproject.org>;
 Wed,  2 Jul 2014 03:09:30 +0000 (UTC)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com
 [IPv6:2607:f8b0:400c:c01::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 837F72D12D
 for <tor-talk@lists.torproject.org>; Wed,  2 Jul 2014 03:09:30 +0000 (UTC)
Received: by mail-ve0-f173.google.com with SMTP id db11so10654668veb.32
 for <tor-talk@lists.torproject.org>; Tue, 01 Jul 2014 20:09:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :content-type; bh=4fzIoMYhWHjAbIpuhmAnoKn0rrZF3YembS/R0pBHVUc=;
 b=nZ/iiBp6JoZU5KSMawGpy1mFrAI19o9nSNvgCGnwOtI35uHngPZSPu35hKdfH15Glx
 XOKAMTalob0pVPQuHBylRlTKZm7qi1zBFBd46F36RQrS483PFBI4lSYu/uFhWQi8o/Mr
 vVhAMzWhyBVwK4sEivk3YXrnoLFyZs/4srl/sVu8OlUtLqFh8joWcJEdv9MQYhJZXBgh
 /0xKK/svcmq39mAHHVNCcklvjBDwCNmfS7uTesRxmW5kQlWQQrodmnjv+yKrMZljmM+i
 ZPDll2T5dymz9/CPsOXypRo3G55opupOqZwyU9pHOaAeAWEXdRgS1SolDKQnKkng5bmz
 R+qQ==
X-Received: by 10.52.231.8 with SMTP id tc8mr3984322vdc.35.1404270567819; Tue,
 01 Jul 2014 20:09:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.152.148 with HTTP; Tue, 1 Jul 2014 20:09:07 -0700 (PDT)
In-Reply-To: <CAJq5o=t00ahx3B7qax8EbWbkDDs+mgk9BEbO3djyi00i8OFszg@mail.gmail.com>
References: <CAJq5o=t00ahx3B7qax8EbWbkDDs+mgk9BEbO3djyi00i8OFszg@mail.gmail.com>
From: Miguel Freitas <mfreitas@gmail.com>
Date: Wed, 2 Jul 2014 00:09:07 -0300
Message-ID: <CAJq5o=vnogoCWn7+dBbz-ym7x38Yb_qYHgW7QoTN_VbsTo6SRA@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Fwd: twister-core 0.9.22: Tor support available
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Hi people,

We have just reached an important milestone: twister is now compatible with
Tor!

http://twister.net.co/

As some people may be aware, the blocking issue from Tor compatibility was
the DHT part. Because our DHT requires UDP and Tor doesn't support it (and
I'd guess it may probably never implement such thing) that was pretty much
a showstopper.

Still, running twister on top of Tor was a long time goal. As discussed in
the white paper ( http://twister.net.co/?attachment_id=355 ), the Tor
support allows a far more interesting threat model.

The solution was to implement the routing of the DHT traffic through other
twister peers. As we already have an unstructured TCP-based P2P overlay
network derived from the Bitcoin protocol, I have just extended this
protocol with the new DHT relaying commands.

So, a few minutes ago, I've been able to successfully run twister over Tor
for the first time, with all functionality. That includes downloading the
blockchain, using DHT to obtain posts, profiles, avatars and the swarm peer
lists from trackers, and also synchronizing post's torrents. All the 3
network overlays were tunneled by the Tor socks5 proxy.

In order to try this feature just add the "-proxy=127.0.0.1" argument to
twisterd command line (assuming your Tor daemon is running on localhost
with port 9050).

It might take some time to reach a few relaying nodes though. This is
probably going to improve over the next few days as people update their
twister clients.

regards,

Miguel
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

