Delivery-Date: Thu, 19 Jun 2014 13:42:22 -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.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	FROM_LOCAL_NOVOWEL,RCVD_IN_DNSWL_MED,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 moria.seul.org (Postfix) with ESMTPS id A2BB61E0A49
	for <archiver@seul.org>; Thu, 19 Jun 2014 13:42:20 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9A7442F870;
	Thu, 19 Jun 2014 17:42:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C807E2F9D1
 for <tor-talk@lists.torproject.org>; Thu, 19 Jun 2014 17:39:45 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 YZtiPxCmVKQq for <tor-talk@lists.torproject.org>;
 Thu, 19 Jun 2014 17:39:45 +0000 (UTC)
Received: from mout.gmx.com (mout.gmx.com [74.208.4.201])
 (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 ABEE62F93F
 for <tor-talk@lists.torproject.org>; Thu, 19 Jun 2014 17:39:45 +0000 (UTC)
Received: from [127.0.0.1] ([99.190.181.188]) by mail.gmx.com (mrgmxus002)
 with ESMTPSA (Nemesis) id 0LnOzQ-1WVns00Pc6-00hbBj for
 <tor-talk@lists.torproject.org>; Thu, 19 Jun 2014 19:39:42 +0200
Message-ID: <53A32034.7050303@gmx.com>
Date: Thu, 19 Jun 2014 12:39:00 -0500
From: Joe Btfsplk <joebtfsplk@gmx.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53A30C94.1080506@gmx.com> <53A31601.7070704@gmail.com>
 <53A317C9.2090409@gmail.com>
In-Reply-To: <53A317C9.2090409@gmail.com>
X-Provags-ID: V03:K0:PNcTdD3Jxtvy46urN21zJONEmcxVfuz9IIGLTztoU5+l912nGbj
 cTwJ695w6zyZqF89TMxcwVobSCByzVdRwpo3n0q7ekU+gLf2x7VxDQQ74CO2Q5pXHI2QHB2
 3nW8mvNinL/HLZGxptjbzWCXPiGMFQssmGrX9ej5Zw5HriZjuPaIq7ZxVUSBWI8Uue738SD
 rgzlJgcLRCtrv6Sm6RrFA==
Subject: Re: [tor-talk] Should DOM storage really be enabled by default in
 TorBrowser?
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


On 6/19/2014 12:03 PM, Aymeric Vitte wrote:
> The problem will be that sites such as Mega will not work any longer
> with TBB but it's not logical to forbid indexedDB and allow localStorage
> (and sites such as Mega should better use indexedDB rather than
> localStorage)
>
> Le 19/06/2014 18:55, Aymeric Vitte a =E9crit :
>> That's exactly what I pointed out in my follow-up email regarding yt
>> streaming.
>>
>> Given that there are no options to disable it or ask for permission in
>> FF, given that FF behaviour is unclear regarding how it is managed
>> (for example blocking 'offline storage' by clicking on the icon on the
>> left of the url + more information/permissions seems to have no
>> effect) and given that it is used by many sites to store cookie-like
>> stuff, I really think it should be disabled.
>>
>> I would disable the cache too since it can give some information that
>> you already visited the place and when.
>>
>> Le 19/06/2014 18:15, Joe Btfsplk a =E9crit :
>>> Curious: Should DOM storage really be enabled by default in Tor
>>> Browser 3.6.x, when other forms of disk storage are disabled?
>>>
>>> If so, why is that?
Thanks.  I'm sure many would enjoy hearing from those directly involved =

w/ TorBrowser, or that consider themselves "experts" on using DOM =

storage in it, why it's necessary or allowed, when by design all other =

forms of disk storage are disabled.
-- =

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

