Delivery-Date: Thu, 02 Jun 2016 17:37: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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	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 3B3131E03D3;
	Thu,  2 Jun 2016 17:37:41 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E5D1FE0F52;
	Thu,  2 Jun 2016 21:37:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A14ADE0F50
 for <tor-talk@lists.torproject.org>; Thu,  2 Jun 2016 21:37:31 +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 h_6YydowXZfl for <tor-talk@lists.torproject.org>;
 Thu,  2 Jun 2016 21:37:31 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 5528CE0F4C
 for <tor-talk@lists.torproject.org>; Thu,  2 Jun 2016 21:37:31 +0000 (UTC)
Received: from cotinga.riseup.net (unknown [10.0.1.164])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id A37651A2767
 for <tor-talk@lists.torproject.org>; Thu,  2 Jun 2016 21:37:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1464903447; bh=icHJwr3Pd74IZwN/SR5wlqgR3Caam1ukt7wHZFz9+GI=;
 h=In-Reply-To:References:Subject:From:Date:To:From;
 b=Us8/kdpvPbV20hTYfYyvFOBQFkqwFyB+zfTsDjkDozIxNgrv1j1W6HWO7RsaV8A9r
 MEw0I7FB+7U+M4VpPg4zxCDEZ00Xdn9IUbFtuS4C0MoY5ALnwWrDE0vX/u4Ihx+NBZ
 npPgb4nMo642LNq93TnKJluKwDnYj70EK3BazCxw=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: flipchan) with ESMTPSA id A108D405FB
In-Reply-To: <CAB7TAMnyTXqqrxyV4Fixu4Ndm=KVqasSSkuvSChTk78X=D5NZw@mail.gmail.com>
References: <CAD2Ti28Qt9YKC69AfSMKAPQ8sDqxnHHpv6wD6Zi8pSeW3cMfaQ@mail.gmail.com>
 <574FF7BF.1020604@avanix.es>
 <CAD2Ti29CZAhtG0YTjnPx=RQ+hPkJAsCgTGd=Sd3U0W_r4uRVag@mail.gmail.com>
 <CAB7TAMnyTXqqrxyV4Fixu4Ndm=KVqasSSkuvSChTk78X=D5NZw@mail.gmail.com>
MIME-Version: 1.0
From: Flipchan <flipchan@riseup.net>
Date: Thu, 02 Jun 2016 23:37:21 +0200
To: tor-talk@lists.torproject.org
Message-ID: <4E3BBE0C-B99E-4C94-80F8-F4254A146A5C@riseup.net>
X-Virus-Scanned: clamav-milter 0.99 at mx1.riseup.net
X-Virus-Status: Clean
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="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

That sounds rly good , Dont u mean more like a random time or date ,sure u could pic a random number what if the number is to high? Or to low,anyhow cool idea

Allen <allenpmd@gmail.com> skrev: (2 juni 2016 17:39:32 CEST)
>>
>> There's nothing you can do about it but
>> - start researching and using networks that use fill traffic
>>
>
>Another alternative would be to re-architect the services of interest
>to
>use a message or packet store-and-forward protocol with a random delay
>to
>thwart traffic analysis.
>-- 
>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

-- 
Sincerly Flipchan
-- 
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

