Delivery-Date: Sat, 12 Jul 2014 09:56:43 -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 95C411E045E
	for <archiver@seul.org>; Sat, 12 Jul 2014 09:56:41 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C00FB2F9DF;
	Sat, 12 Jul 2014 13:56:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0105421525
 for <tor-talk@lists.torproject.org>; Sat, 12 Jul 2014 13:49:02 +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 PEc7tqRotddp for <tor-talk@lists.torproject.org>;
 Sat, 12 Jul 2014 13:49:01 +0000 (UTC)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com
 [IPv6:2a00:1450:400c:c03::231])
 (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 A35CF21519
 for <tor-talk@lists.torproject.org>; Sat, 12 Jul 2014 13:49:01 +0000 (UTC)
Received: by mail-we0-f177.google.com with SMTP id u56so2250219wes.36
 for <tor-talk@lists.torproject.org>; Sat, 12 Jul 2014 06:48:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=v5bW+sA86SzyyVs4lXVglADdPc8QoAWX5007lCJAb8c=;
 b=ST/2nO6ejeWmzAobyePUGt+pQA7UCTrfnsWcu3jyrmIPixT82tv6ZUn8+Jd3thPrWe
 eSxCPH5Pq7Dy0yLUVCrkmDR9hOfoSpr9AbkI9/ONckhRTxZLZYKIA3EnZhYjBzZMNucs
 TLOXdvzJEbTV8sK/tl16oH2zodw80TOrM9UnMbtrIp0hms0H0MYKAvIaeeFpgmgviYp/
 AoOIGZsOJwI7DGgTSY56uNNDd7sdUcgXIfGJr/BASZQ1CZJLxCCjIn6vGW0jROVl6mf/
 ilRnZe41sBDWmDpzMim92WjJOF6iPglfU0dvpQdD8EfjuI0zZTFzAUhAwOg56Qu70oBh
 O2vA==
X-Received: by 10.194.222.230 with SMTP id qp6mr6817025wjc.23.1405172937104;
 Sat, 12 Jul 2014 06:48:57 -0700 (PDT)
Received: from [192.168.1.11] (ANice-652-1-365-191.w83-201.abo.wanadoo.fr.
 [83.201.200.191])
 by mx.google.com with ESMTPSA id ex4sm7027366wic.2.2014.07.12.06.48.55
 for <tor-talk@lists.torproject.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Sat, 12 Jul 2014 06:48:56 -0700 (PDT)
Message-ID: <53C13CC8.6070702@gmail.com>
Date: Sat, 12 Jul 2014 15:48:56 +0200
From: Aymeric Vitte <vitteaymeric@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAP3fC8Q548JhJtP880WKkqc-raWMw8+Qxhn0KVGSdiMZFyQefQ@mail.gmail.com>
 <CAOsGNSQZov6PG-g8_W4V6BvT34aZWSKm0k0-ZdBc4uVM6=okxQ@mail.gmail.com>
In-Reply-To: <CAOsGNSQZov6PG-g8_W4V6BvT34aZWSKm0k0-ZdBc4uVM6=okxQ@mail.gmail.com>
Subject: Re: [tor-talk] Putting the "Tor" back in Torrent
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


Le 12/07/2014 06:58, Zenaan Harkness a =E9crit :
>> ## What do you say?
> Go for it.
No, I would not advise this, whatever Helder's arguments are, this can =

not work, even if you  get a lot of peers that expand the network you =

will still have the bottleneck of the Tor nodes, which are not numerous =

enough, managed by a centralized system as you mention, not compatible =

at all with a real P2P system.

What can work is a separate P2P network (maybe) based on the same =

concepts (maybe --> again, I would not take the model of hidden services)

For Helder & team, did you really test up to now what it takes to =

establish (good) circuits in the Tor network and do you have an idea of =

the "real-time" average number of nodes that are behaving correctly? And =

performances, lifetime of the circuits?

-- =

Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

-- =

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

