Delivery-Date: Tue, 23 Jun 2015 00:06:53 -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=-3.1 required=5.0 tests=BAYES_00,BODY_URI_ONLY,
	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 C14911E0B59;
	Tue, 23 Jun 2015 00:06:51 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A6E963644D;
	Tue, 23 Jun 2015 04:06:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 01B0C3644A
 for <tor-talk@lists.torproject.org>; Tue, 23 Jun 2015 04:06:44 +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 Ho3A2jaMRLhR for <tor-talk@lists.torproject.org>;
 Tue, 23 Jun 2015 04:06:43 +0000 (UTC)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com
 [IPv6:2607:f8b0:4001:c03::22d])
 (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 D4E1136449
 for <tor-talk@lists.torproject.org>; Tue, 23 Jun 2015 04:06:43 +0000 (UTC)
Received: by iebrt9 with SMTP id rt9so3602360ieb.2
 for <tor-talk@lists.torproject.org>; Mon, 22 Jun 2015 21:06:41 -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
 :content-type; bh=bxNcpadFObU/iCIjAStwhWepuAZIKUm7JiKJxFEtnZc=;
 b=wZotlDaSNfXH/ETrE2V0ZpP4oUaihHb7YYTR6Yvav9K3x6kjvnX5GXAOfl/jS8Urvw
 Ylloj6myg6kTI80c6it7Z85zVxNY31+dRddXXTRTHp9rRX/ZqF5XIB4IClWHHiWmVVLq
 zk4FcyRLy8TTWp5a1XpA48mJa2njf6ZgWfSD48Lkyme2pBF1ISXadFC5lUMtzs0WTtQ3
 bOkYGkoQSO7sYeiBXQH5jv7g9JJ/IdVBilmaWf2ToF/+5SwbaMluqNDkm/3uzg6pNAQf
 +b7DWipR/F8U6thZI8IkzsMgVfj0rLUH9VGda7+Cr8VPH5Qb+4p1R8t2hjFG0sVjgoun
 uywQ==
MIME-Version: 1.0
X-Received: by 10.107.4.204 with SMTP id 195mr23462062ioe.40.1435032401601;
 Mon, 22 Jun 2015 21:06:41 -0700 (PDT)
Received: by 10.36.107.140 with HTTP; Mon, 22 Jun 2015 21:06:41 -0700 (PDT)
In-Reply-To: <20150621155532.GB1643@vpn212046.nrl.navy.mil>
References: <CAD2Ti2-xVw_W2YDqkdQHmcHyKBDQjfT5jvc-8m3EAU8UkqxrUA@mail.gmail.com>
 <55864B5C.6070509@cock.li>
 <20150621155532.GB1643@vpn212046.nrl.navy.mil>
Date: Tue, 23 Jun 2015 00:06:41 -0400
Message-ID: <CAD2Ti29UY7n=vwEPODtqzQoGsh7knEGSKz1bJqDb+nDF3YEaUQ@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Matryoshka: Are TOR holes intentional?
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>

Longer reply may come, but I think it is useful to again say
that it may be that you must disassociate the classical "tor
centric" idea of fill away from the idea of filling the "tor circuit".
Of course any circuit level fill from end to end will still be visible.
But if the network itself is doing its own node to node fill underneath,
independant from whatever circuits ride on top, there may be
your answer regard to the casual looker of GPA.
-- 
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

