Delivery-Date: Tue, 23 Jun 2015 20:12:17 -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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 89EEB1E016C;
	Tue, 23 Jun 2015 20:12:15 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C750A36765;
	Wed, 24 Jun 2015 00:12:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id DC3C73673F
 for <tor-talk@lists.torproject.org>; Wed, 24 Jun 2015 00:12:06 +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 bvdHbQy7br4D for <tor-talk@lists.torproject.org>;
 Wed, 24 Jun 2015 00:12:06 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 8B04C36604
 for <tor-talk@lists.torproject.org>; Wed, 24 Jun 2015 00:12:06 +0000 (UTC)
Received: from localhost ([171.25.193.78]) by mail.gmx.com (mrgmx101) with
 ESMTPSA (Nemesis) id 0M9OMc-1ZFm2e2iMw-00CgXi for
 <tor-talk@lists.torproject.org>; Wed, 24 Jun 2015 02:12:03 +0200
Date: Wed, 24 Jun 2015 02:14:13 +0200
From: =?utf-8?B?w4dhxJ/EsWwgUC4gxZ5lc3Rv?= <secpost@abwesend.de>
To: tor-talk@lists.torproject.org
Message-ID: <20150624001413.GD752@localhost.localdomain>
References: <CAD2Ti2-xVw_W2YDqkdQHmcHyKBDQjfT5jvc-8m3EAU8UkqxrUA@mail.gmail.com>
 <55864B5C.6070509@cock.li>
 <20150621155532.GB1643@vpn212046.nrl.navy.mil>
 <CAD2Ti29UY7n=vwEPODtqzQoGsh7knEGSKz1bJqDb+nDF3YEaUQ@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAD2Ti29UY7n=vwEPODtqzQoGsh7knEGSKz1bJqDb+nDF3YEaUQ@mail.gmail.com>
User-Agent: Mutt/1.5.23+89 (0255b37be491) (2014-03-12)
X-Provags-ID: V03:K0:cAL43G3u61HeNoj2IetDrLkNZQr6f4s1TUxiv4v/yvYcGPcTrqO
 IVtIwPlKHWe4pCQsKh7Y4mpZtvzNfHGCh9IiZ29wNo9XEC1ewLlcpx6OEID5VsxjMqmW53i
 Waf2nm5TenrktCURwjOHgi94QCoF/qWa58+IOf5bRF683MNA9MH5muCGGROcLHxuI7GSY2G
 /G0orxYAjJreSnPoHEYxQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:EYxsOJ0HMzI=:gNRA2lbBo8hJ27qfuxT2EX
 sG8zPYT+wJogE0NTQaR9yKIhG5PGOBc8pg2/bl/ydrZuAZ7GWL4KeqpiHpYXUzCY8mFHJBF3H
 YaKVLCKaYiRmxiJMr3K853ae8VpEMGdwxjKGophEJzcVlDagiEum0l7ik8ujhMFhredu9Gh35
 pQh9mVaQ5Et7tnb++lsjO9k1C1FQgZntOY/rv8kpnXt0Suvw7/YIR1n8Eo768+qlQlTU8+8Hm
 R72a/DbzMeBbJztDnrAt5QOFINKe4jhQq+ExXo9wq+05VMvUj86xi7/9Olto3lP/iTZAWT/F/
 MOIFW4t6vsgzB1EoAODVQZhSL6bby0rAsoZrP5omJ+Nn42awRkPcNmfc3ezgy3OxXcYulGvET
 /5anAmdTEEQNThSm6x8BQQAokLQufwSUpcs11uG5KUT0Pl+YD1KlPAP8yb4WcQB0yFCfKSjQG
 1zRjEYJl4RI+xmrmhTdh6niZWQSCMwYr7hp4y1UgltzauIREJ1cqPAE0BWBXFKRyJ2hO8uCUQ
 KGz/G3943Ne8L/dVCGjh+k00daQctjNtXZsPQ3a7qMEwdOwsUxIiLBDgS3EOsyALHQNQA1nXp
 l1A/AhMclIH1kYHdpUhUEDVOuTNUBMWKU3cZ1KQyxL4WrhhUNQYpVPbF2gukBMbTR9PYjy4qA
 i32H6rYNHuTnSnqx23WYdRYYCXlx/AEss/r6TRxmKoKDwpK7m5Q8Xr14VwlZ05+upebk=
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>

On Tue, Jun 23, 2015 at 12:06:41AM -0400, grarpamp wrote:
> 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".

There is no benefit in padding, it does the opposite what endpoints want 
from tor: data and anonymity.

Find an application that moves data, and the application that comes to mind
is filesharing. Face it, tor would grow into a massive network. If you consider
the size of 6000 relays, this idea is scary. Node participation in filesharing 
networks is often tenfold the size of tor nodes recorded in consensus.

Or video streaming via HS, distribute the data to your clients, peer
them together in a DHT.

These approaches are better than feeding nonsensical data into
circuits, let's feed real data into them, it is beneficiary for
the networks participants, they want it.

Anoter approach is to attract traffic inbound and make the same destination
emit at various places that aren't strictly in the consensus: cdn as HS 
can do that, without any modification of tor protocol or consensus.

Imagine wikipedia, the mozilla foundation running a HS. I'd rather see
my browser and my extensions coming from official mozilla hidden service
cdn, than via shady exitnode (no offense to all you sweet exits).

If you operate a CDN run a HS on an isolated edge. It won't emit
anything that you already have seen, since users may access your net
already via tor. Adversaries already try to compromise it using tor.
Technically, there is no difference in operations.

If you operate a CDN that has excess capacity, consider running
an exit at your leisure, with an exit policy that benefits you, your
customers. You don't have to serve all the participants of the tor
network.

If you utilize a CDN ask them about running a HS or an exit for you, 
since it may be beneficiary for your customers that already use tor.

The only centric idea of tor, its the authoriry of distributing consensus data,
it works suprisingly well. I really doubt you find better suited individuals
for that job.
-- 
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

