Delivery-Date: Tue, 03 Jun 2014 03:11:46 -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.9 required=5.0 tests=BAYES_00,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 6C5E81E0941
	for <archiver@seul.org>; Tue,  3 Jun 2014 03:11:44 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1998826267;
	Tue,  3 Jun 2014 07:11:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 79A6A2E2C9
 for <tor-talk@lists.torproject.org>; Tue,  3 Jun 2014 07: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 o8Ntvs-JVDVh for <tor-talk@lists.torproject.org>;
 Tue,  3 Jun 2014 07:04:35 +0000 (UTC)
X-Greylist: delayed 1993 seconds by postgrey-1.34 at eugeni;
 Tue, 03 Jun 2014 07:04:35 UTC
Received: from Mailamir.com (mailamir.com [198.27.109.33])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 629AE28CCE
 for <tor-talk@lists.torproject.org>; Tue,  3 Jun 2014 07:04:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by Mailamir.com (Postfix) with ESMTP id B581F20EBB
 for <tor-talk@lists.torproject.org>; Tue,  3 Jun 2014 02:34:28 -0400 (EDT)
X-Virus-Scanned: amavisd-new at Mailamir.com
Received: from Mailamir.com ([127.0.0.1])
 by localhost (Mailamir.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id YMzgWPCA6HPk for <tor-talk@lists.torproject.org>;
 Tue,  3 Jun 2014 02:34:28 -0400 (EDT)
Received: from [192.168.0.251] (ppp118-209-6-129.lns20.mel4.internode.on.net
 [118.209.6.129]) by Mailamir.com (Postfix) with ESMTPSA id 7401E20075
 for <tor-talk@lists.torproject.org>; Tue,  3 Jun 2014 02:34:23 -0400 (EDT)
Message-ID: <538D6BB5.5070505@gassiep.com>
Date: Tue, 03 Jun 2014 16:31:17 +1000
From: Naz Gassiep <naz@gassiep.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <b737f3eec6a08de93101cf7c1ad8a365@172.16.17.3>
 <538C832B.3080309@mozilla.com> <538CA5A8.9050304@riseup.net>
 <538D1CF2.5000800@cyblings.on.ca>
In-Reply-To: <538D1CF2.5000800@cyblings.on.ca>
Subject: Re: [tor-talk] canvas fingerprinting
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 3/06/2014 10:55 AM, krishna e bera wrote:
> What if all the HTML5 and CSS3 calls to read back any data in 
> Javascript returned null or some 5xx (not allowed) error code? Web 
> pages should be a write-only media just like print. It would seem 
> reasonable for a browser in "privacy mode" to implement it that way. 
<pedant>
Read-only.
</pedant>

However, yes I agree that private browsing should default to read-only, 
as any time you interact, you expose something of yourself, whether by 
what you're responding to, how you write, or what view or opinion you 
are expressing. Tor users need to be aware that any interaction while in 
privacy mode is a liability, and it is proper that they have to actively 
enable some option to enable interaction.
- Naz.
-- 
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

