Delivery-Date: Fri, 20 Jun 2014 10:12:47 -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 khazad-dum.seul.org (Postfix) with ESMTPS id 2EEDE1E0A01
	for <archiver@seul.org>; Fri, 20 Jun 2014 10:12:45 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 92D513021B;
	Fri, 20 Jun 2014 14:12:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 08297301FF
 for <tor-talk@lists.torproject.org>; Fri, 20 Jun 2014 14:04:35 +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 di-Pi0EipZpP for <tor-talk@lists.torproject.org>;
 Fri, 20 Jun 2014 14:04:34 +0000 (UTC)
Received: from mout.gmx.com (mout.gmx.com [74.208.4.200])
 (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 DBE11301F6
 for <tor-talk@lists.torproject.org>; Fri, 20 Jun 2014 14:04:34 +0000 (UTC)
Received: from [127.0.0.1] ([99.190.181.188]) by mail.gmx.com (mrgmxus001)
 with ESMTPSA (Nemesis) id 0LlmMg-1WOvj60Aca-00ZLnN for
 <tor-talk@lists.torproject.org>; Fri, 20 Jun 2014 16:04:32 +0200
Message-ID: <53A43F79.8040603@gmx.com>
Date: Fri, 20 Jun 2014 09:04:41 -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> <53A33139.7050405@torproject.org>
In-Reply-To: <53A33139.7050405@torproject.org>
X-Provags-ID: V03:K0:JMC9VWP9y+FJp4gfFxOYtiyAQDn4yRlYMB8lCnGmZ06d5cSHEu4
 nIP7cJHs9voU92sy+RhQeAkrMS7v5449eJowuH7FE07H5S3JlbNRrbyEp9qUKhdou3A5Qsx
 +UqALazVn4vR190Ljm0fUKQwWKuvSlD+UjU7Dy4uMi35ugkQku2t8w3F4T/81ARfbeFeewA
 8ufC3JVEL94O/wV+TZ0GQ==
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


On 6/19/2014 1:51 PM, Georg Koppen wrote:
> Joe Btfsplk:
>> Curious:  Should DOM storage really be enabled by default in Tor Browser
>> 3.6.x, when other forms of disk storage are disabled?
> DOM Storage in Tor Browser does not save state to disc. And it is bound
> to the URL bar domain (see design document).
>
> The code is in commit 5392d2ed679eaaa078f5c667573ef0698ec65345 in the
> tor-browser repository.
>
> Georg
>
>
Checking vanilla Fx, I don't see it's *storing anything* in 
webappsstore.sqlite either, even though the default about:config entry 
"dom.storage.enabled" = true.
Maybe? that's because I have all disk cache disabled in vanilla Fx, as 
is Torbrowers' default?

Unless youtube doesn't attempt to use DOM storage, with 1st party 
cookies & java script allowed for both youtube.com & ytimg.com, in 
vanilla Fx.

It's good nothing's being stored (even in Fx), except you can't verify 
which delete history / cache / storage method removes DOM data.
Something else must be going on.

BTW, the "Design Document - DRAFT" (dated March 15, 2013 ) that's linked 
from TorProject's main page, has non-functioning link for the patch in 
the line below about DOM storage.
It says "404 - Cannot find file"

 1. /DOM Storage

    DOM storage for third party domains MUST be isolated to the url bar
    origin, to prevent linkability between sites. This functionality is
    provided through a patch to Firefox
    <https://gitweb.torproject.org/torbrowser.git/blob/maint-2.4:/src/current-patches/firefox/0026-Isolate-DOM-storage-to-first-party-URI.patch>./


-- 
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

