Delivery-Date: Sun, 20 Mar 2016 19:30:04 -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 [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 2216E1E0AA9;
	Sun, 20 Mar 2016 19:30:01 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 83E2E38920;
	Sun, 20 Mar 2016 23:29:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 257E831E3F
 for <tor-talk@lists.torproject.org>; Sun, 20 Mar 2016 23:29:52 +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 ef6eME8We9jk for <tor-talk@lists.torproject.org>;
 Sun, 20 Mar 2016 23:29:52 +0000 (UTC)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com
 [IPv6:2607:f8b0:400c:c05::234])
 (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 F1415388EB
 for <tor-talk@lists.torproject.org>; Sun, 20 Mar 2016 23:29:51 +0000 (UTC)
Received: by mail-vk0-x234.google.com with SMTP id q138so105938738vkb.3
 for <tor-talk@lists.torproject.org>; Sun, 20 Mar 2016 16:29:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc; bh=6cNuMPuKJkAnrc/UuLcQAKswhrAdhg+8KwK/PnuwcVE=;
 b=jVarohOZ9xwgs2ClQrjNt8awGoMub1fI2I/AprtdhZqYg4DEg/7lTjAVK/7YYcJilo
 E9f49nLnk5t7FaobtEwbF0ifQ1fEgaF9zqp9DVo66U0sAtYraikh7k2pe05adF9GCKCu
 S73eN2d1MYhVzxNiYysXx9UuRqi3qtc0K59ioyimB0PT0U8KCxw8ZK5+MeYQLyse4pBL
 7KCmufr/BbK1tH6OECW3bfBUNkxFFhdfyZ4jXt5L6S4msT0JPlVhE9tBIy/F6ERxRyxr
 1Hxz08eWQC5w0DTaMXupDEJbf8dMRnpYefr4RPu0VkQV4EftW1niQn84Dbh3EHryEI7g
 NMPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:cc;
 bh=6cNuMPuKJkAnrc/UuLcQAKswhrAdhg+8KwK/PnuwcVE=;
 b=LDDGW3ecF2QKWCSM+7tQB6uVfhCme/NfxME6AjMuqKaDVPDSpPftOI002a2LfGHPBr
 awa1mDDEFafOOjGg89LkUcyexSm1e/Yyrd0CiYQ/V+kcbkLXx5jEXR4TGMwo7G5gRi8F
 K6uz+UZVqNE8rYp3DvkUJdQSe/mr3S+M8zn+0TO9KVLkM9DOxwja1gQXc0CTGIrZLMIg
 g8T0bJPr/kV9b2HHsjVCE92W7WT9EmKXyrGEEPy6tqNpPYsoWGYVdzrBMYD7cOZPyGNc
 YwBEN2klYJNDqVgMR9sbDmrKjfY9iIP0eRisYALdnvkccMTrRvu/ZthEa12CVZBz32XE
 HpxQ==
X-Gm-Message-State: AD7BkJIajSfNBUCcbygd1H4JBYGYJ2OQwlGpZ46KqvMIPFZf0CulBL/LWNmnqFqM9b+f4JMjh3POqFX7IAxOSg==
MIME-Version: 1.0
X-Received: by 10.31.136.5 with SMTP id k5mr25380635vkd.35.1458516589584; Sun,
 20 Mar 2016 16:29:49 -0700 (PDT)
Received: by 10.176.69.5 with HTTP; Sun, 20 Mar 2016 16:29:49 -0700 (PDT)
In-Reply-To: <20160320221427.GE15350@torproject.org>
References: <nci43k$3ee$1@ger.gmane.org>
 <CAJVRA1SOk_FBO7wXi_tHbFzfPdG21KK5M++45iGcv9tJ8uRs3A@mail.gmail.com>
 <20160319034044.GQ8732@moria.seul.org> <ncjbkj$tfr$1@ger.gmane.org>
 <20160320015647.GR8732@moria.seul.org> <ncn0rr$1jm$1@ger.gmane.org>
 <20160320221427.GE15350@torproject.org>
Date: Sun, 20 Mar 2016 19:29:49 -0400
Message-ID: <CAD2Ti2-U7L7kJBSUSLhpwZFd0Lo77WOWbPGtAGnoz65ytaXc5A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Cc: cypherpunks@cpunks.org, cryptography@metzdowd.com
Subject: Re: [tor-talk] Traffic shaping attack
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>

On 3/20/16, Mike Perry <mikeperry@torproject.org> wrote:
> It could also be due to the fact that Tor is effectively
> single-threaded. If something on the user's guard node, intermediate
> node, or hidden service is taking large amounts of CPU time, this will
> prevent traffic from flowing while that operation is happening. See:
> https://trac.torproject.org/projects/tor/ticket/16585 (though that
> ticket could use some help with clarity).

Related... why a traffic fill solution may need to reclock and transmit new
own random jitter and self limit to processable / expected bandwidth contracts
to mask network induced computation and provide for CPU headroom therein.

As with [John Gilmore's?] IEEE fill layer suggestion, there should be
a group establish outside just Tor calling for participants to look at
various crypted network fill models against now known / surmised G[P]A
methods.
-- 
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

