Delivery-Date: Wed, 24 Dec 2014 12:09:05 -0500
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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,URIBL_BLOCKED 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 9934A1E0100
	for <archiver@seul.org>; Wed, 24 Dec 2014 12:09:03 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id AB5DF3239A;
	Wed, 24 Dec 2014 17:08:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9775A32398
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:08:24 +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 CbUDgDXQu1-b for <tor-talk@lists.torproject.org>;
 Wed, 24 Dec 2014 17:08:24 +0000 (UTC)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com
 [IPv6:2a00:1450:400c:c00::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 435DF3209D
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:08:24 +0000 (UTC)
Received: by mail-wg0-f54.google.com with SMTP id l2so11727668wgh.27
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 09:08:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=cyblings.on.ca; s=google;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=Yu9PFxJVXcXA0rz0KDHhL6Ak03l+9YOwrK81lrJ15Pw=;
 b=czlKaJTi8mMC0pSGbGMQorZrz0Lkbbu6akDX//AM6vfBD4LJHaKkK+No8741NpWKtd
 6h0mv9p3bRun/QJLWbvAkujSXx9LwXPdI+h3eQ+rkxVHqCJZpqJYupv7uWYCuC/b8bOV
 Gnrg9/AihCoaHRl0mK//AZHsJDuUuYxxfc93Q=
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:content-type;
 bh=Yu9PFxJVXcXA0rz0KDHhL6Ak03l+9YOwrK81lrJ15Pw=;
 b=bd043Pls8AXxLuos6DZqt076w4B5IBOT5YplzHOD4dx52mIooPqjgqCtCYT+FhIjwc
 85H2Q7y6ZwadDTYkDiGnVrnQZLlovLFouj5LbVL+M0FKBmbqd3Fglk9mBTEp9jaqGHZk
 fjnGK1YcuyqU+BWapwd1SBysAeltQlf4wJDon834F1rHKZRyXxQb7rBuQWvDpYQWEhz1
 0wgK1mTwAoFKgzK23MW/l52dPizF4yCNlzdKnBvTQGqzcg1gWSbyOesfDroD+tO57KM4
 iqSKZuqKmAo+5hbvgZ07WioXYxJ/Joilgayo42SihYDfRcwwQJkORRxXYJCnhiw9b+ne
 pvTQ==
X-Gm-Message-State: ALoCoQmc6hukcDcuCH0Z8go0pwov7rMHXVE14Vi9my/xvc/jVkZ8WWA2ckIHZ+cguICZwULfRQEe
MIME-Version: 1.0
X-Received: by 10.194.22.6 with SMTP id z6mr62866349wje.55.1419440901312; Wed,
 24 Dec 2014 09:08:21 -0800 (PST)
Received: by 10.27.210.207 with HTTP; Wed, 24 Dec 2014 09:08:21 -0800 (PST)
X-Originating-IP: [65.93.71.229]
In-Reply-To: <20141221174459.GD8014@moria.seul.org>
References: <548EE5A5.5060901@riseup.net> <85sigh3q5w.fsf@boum.org>
 <20141221174459.GD8014@moria.seul.org>
Date: Wed, 24 Dec 2014 12:08:21 -0500
Message-ID: <CAF6_1m9zg=-tcY=cBH8HX8NLCOgcFHk0uiLvD_vY=yn19poqxQ@mail.gmail.com>
From: krishna e bera <keb@cyblings.on.ca>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Including Adblock to TBB to save bandwith
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>

What about making a TorProject filter list for Adblock* users so that
we all look the same to sites visited?

Or go further and include (or add some functionality of) RequestPolicy
into TBB.  Its purpose is to ensure no URLs outside the domain you
intended to visit are opened, and the user has to set up the
cross-domain whitelist.  Of course that breaks many Web 2.x(tm) sites
but Torproject or a usergroup could make a set of initial rules that
cover important sites and vetted https script sources such as jquery.
Being in control of what gets into your browser seems to me a higher
priority for those concerned with security and privacy than placating
advertisers or reducing bandwidth.

On Sun, Dec 21, 2014 at 12:44 PM, Roger Dingledine <arma@mit.edu> wrote:
> On Mon, Dec 15, 2014 at 04:10:03PM +0100, intrigeri wrote:
>> Hi,
>>
>> Justaguy wrote (15 Dec 2014 13:44:05 GMT) :
>> > What if torbrowser would include adblock, this would reduce the amount of bandwith
>> > used, and thus increase the overal speeds @ tor
>>
>> See "5. No filters" in
>> https://www.torproject.org/projects/torbrowser/design/#philosophy
>
> Yep. These are some good reasons to keep adblock et al out of Tor Browser.
>
> Another good reason mentioned on this thread is limiting attack surface.
>
> But that said, here are two good reasons to put it in:
>
> A) Reduction of bandwidth, as the original poster here pointed out.
> As a bonus, since some pages don't render until certain of the components
> are there, by fetching fewer components we could see speed-ups that are
> more than just about bandwidth.
>
> B) Potentially significant anonymity gains against certain attacks. If
> traffic confirmation attacks are trivial (I'm not saying we know they are,
> but it's simplest to act as if they are), and websites with ads cause you
> to reach out to many more destinations than you would otherwise, then each
> of those new destinations presents a new risk that an adversary could see
> traffic going over that path. Thus reducing the number of destinations --
> especially common ones like the centralized ad servers -- could help a
> lot against this attack.
>
> For more context, see the "The paper also makes me think about exit
> traffic patterns" paragraph in
> https://blog.torproject.org/blog/improving-tors-anonymity-changing-guard-parameters
> and the discussion around it.
>
> --Roger
>
> --
> 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
-- 
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

