Delivery-Date: Fri, 03 Jun 2016 05:58:16 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	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 [138.201.14.202])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 1864E1E03D2;
	Fri,  3 Jun 2016 05:58:14 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7D904E1055;
	Fri,  3 Jun 2016 09:58:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0FE87E100F
 for <tor-talk@lists.torproject.org>; Fri,  3 Jun 2016 09:58:00 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 BDErN4_6lB5Y for <tor-talk@lists.torproject.org>;
 Fri,  3 Jun 2016 09:57:59 +0000 (UTC)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com
 [IPv6:2a00:1450:400c:c09::235])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id E02AEE0FF8
 for <tor-talk@lists.torproject.org>; Fri,  3 Jun 2016 09:57:59 +0000 (UTC)
Received: by mail-wm0-x235.google.com with SMTP id s131so8781796wme.0
 for <tor-talk@lists.torproject.org>; Fri, 03 Jun 2016 02:57:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to; bh=ieX0NLdVRcc/jIyoqFtMamUJE35mphZ1Aa7L3ILTYiA=;
 b=Dki9/Q5mR1ThlXIOezfue5wkhSWo3pqPZJpeNHLdEpzJhTD2w18kIREXuFMNRvqhlF
 oNSeEfECXlcp4PzhDaM/dsO3imbyyR1Nje3nUhO+w/GPRumwpFSU/BYe9qChEWk1g/50
 KNYN6e7n2ZAXYZx4aF/LJmikQuVJzV8JWQ743xwckgNmP4DKgz9zIxjumURLqEqnMLtD
 JQJkaqm7k/O+/FjEH5C14D6RYsMw/9TTRTgqQRpAgpWfSxGzCDkjDjOzLjMBV+P8JZGn
 1JrjAn82q00ch1LEBoXE6bXLdSiUhDhZL30j2ypkYZaJLxdV4GNjeQUAex/d3X1uHYzh
 FgvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:subject:to:references:from:message-id:date
 :user-agent:mime-version:in-reply-to;
 bh=ieX0NLdVRcc/jIyoqFtMamUJE35mphZ1Aa7L3ILTYiA=;
 b=ivskZeerya6e7Jl16mcCjnC9sW9Rzmd6bOUrrxb+mSKleg7d8h1L6uuZw4tc7lUjw5
 gKJBvqTpwbuNCLtEM0UEFYCSY6oDgGzZOkTVBpjYr7bAieXX4ZTBP09EuFzylj4UUIvx
 x+ypBaQ8mL5zzqaqhDRcfIx+EYVXRRHrw0FtwluQ4/s7ffkY8BTiJBMxMJYEpJU37u4l
 eNOo7NHYaxWD9bgJ2qDUCb+V8pVlKfx/YolCt+fI0YrIPngYXIvyUA5d2nDoBIoyHvmk
 FTCgVugXBCCiARtkn1qsbcpoJkFPBuUsAS+8Dhxeu+bbdr42A06DgmFNtZoDd7zGS2Xp
 omtg==
X-Gm-Message-State: ALyK8tI0vs8wKcM5PkEHj+0IG3kmEFbSUr9SG8mdcqZ7kKAiU/HtUPMVj2JDZoG0dCR+qg==
X-Received: by 10.194.141.16 with SMTP id rk16mr2489911wjb.63.1464947877474;
 Fri, 03 Jun 2016 02:57:57 -0700 (PDT)
Received: from [192.168.1.10] (ANice-654-1-50-28.w83-201.abo.wanadoo.fr.
 [83.201.221.28])
 by smtp.googlemail.com with ESMTPSA id c2sm5605068wme.4.2016.06.03.02.57.56
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Fri, 03 Jun 2016 02:57:56 -0700 (PDT)
To: tor-talk@lists.torproject.org
References: <CAD2Ti28Qt9YKC69AfSMKAPQ8sDqxnHHpv6wD6Zi8pSeW3cMfaQ@mail.gmail.com>
 <574FF7BF.1020604@avanix.es>
 <CAD2Ti29CZAhtG0YTjnPx=RQ+hPkJAsCgTGd=Sd3U0W_r4uRVag@mail.gmail.com>
 <CAB7TAMnyTXqqrxyV4Fixu4Ndm=KVqasSSkuvSChTk78X=D5NZw@mail.gmail.com>
 <CAD2Ti280dofTBwGO+y2s2-UP2deEznhrF5E996nLXbwepRvtQQ@mail.gmail.com>
 <8d3f6f22-8ea0-2c1f-dc0b-0e73617cce34@gmail.com>
 <CAD2Ti29=VpBf6bFOR4ZzczqzAnenMhAwRGkScJaXokFvRpWxaA@mail.gmail.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <85be0732-1d01-d440-bb7f-b41f244dac14@gmail.com>
Date: Fri, 3 Jun 2016 11:57:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:45.0) Gecko/20100101
 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAD2Ti29=VpBf6bFOR4ZzczqzAnenMhAwRGkScJaXokFvRpWxaA@mail.gmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Tor (and other nets) probably screwed by Traffic
 Analysis by now
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="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>



Le 03/06/2016 =E0 07:43, grarpamp a =E9crit :
> On 6/2/16, Aymeric Vitte <vitteaymeric@gmail.com> top posted without trim=
ming:
>> Yes: https://github.com/Ayms/node-Tor#convergence
>>
>> Let's imagine that one Tor circuit reaches a P2P network (here browsers)
>> and is splitted between different peers (UDP) circuits before
>> reasynching to a relay or end point, then the reconciliation from the
>> source to the end point is quite unlikely
>>> Is there any group / list that is actively researching
>>> or developing such networks? Or that wants to?
> If I remember right you're doing file caching / serving
> in the browsers-as-torrent-nodes layer. Yes that
> asynchronous would seem to break end to end timing.
Yes and different upload bandwidth of the peers make the timing
correlation even more difficult
>
> But the 654321012 byte file "into one tor circuit" from
> user at one end would still count same bytes out to
> a "reasynching end point" user at the other end.
> (Or users plural if requested by more than one user).
> Between otherwise relatively quiet endpoints / users.
>
> If they are all shuffling around encrypted bits fulltime,
> without being driven to do so by end user demand,
> such that the start and stop of the bytes of the poster
> and requestor[s] can't be delineated, that looks more
> generally like the fill traffic.
Here we could have some packets that are lost by the peers, because of
UDP, because a peer left and broke a P2P Tor circuit, etc, then the
packets must be resent and x bytes sent is then not equal to y bytes
received, more generally it could be possible to send consciously
several time the same packets who will be dropped by the reasynching end
point, still x bytes sent will be equal to x bytes received at the end
point but not further, that's one of the topics of the project, to be
studied...

-- =

Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
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

