Delivery-Date: Sat, 28 Jun 2014 09:41: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 C875E1E033D
	for <archiver@seul.org>; Sat, 28 Jun 2014 09:41:45 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9F8F42F931;
	Sat, 28 Jun 2014 13:41:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1B1632F7E9
 for <tor-talk@lists.torproject.org>; Sat, 28 Jun 2014 13:29:26 +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 wwwT7c9PbBPV for <tor-talk@lists.torproject.org>;
 Sat, 28 Jun 2014 13:29:26 +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 EFE162D826
 for <tor-talk@lists.torproject.org>; Sat, 28 Jun 2014 13:29:25 +0000 (UTC)
Received: from [127.0.0.1] ([99.190.181.188]) by mail.gmx.com (mrgmxus001)
 with ESMTPSA (Nemesis) id 0LnPBo-1WS7lk1lza-00hfoB for
 <tor-talk@lists.torproject.org>; Sat, 28 Jun 2014 15:29:22 +0200
Message-ID: <53AEC2F9.6080701@gmx.com>
Date: Sat, 28 Jun 2014 08:28:25 -0500
From: Joe Btfsplk <joebtfsplk@gmx.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53ADB7A6.7080709@gmx.com> <20140628095417.GA7408@moria.seul.org>
In-Reply-To: <20140628095417.GA7408@moria.seul.org>
X-Provags-ID: V03:K0:1E+YyL7sc/bLxB1zrZrZaVGhyLK4FlgXQ1v5uz18rv0XCC3tURY
 fNwCxAEmE6IS8mUWKFRXHpRjTM/Wd/Xk27iwDDItSy6rsfLOl/Cygc94ytZsbrgkqMOXIzs
 FEG0U3u71eCVSnww53NJ81Qo/f0oMipocVMLy7TvnSpYfy8yObIQWhsp/MrVfdszb3ns2X8
 YoN5/yWckcLxe75H6D4/A==
Subject: Re: [tor-talk] hardware acceleration OK or not?
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/28/2014 4:54 AM, Roger Dingledine wrote:
> On Fri, Jun 27, 2014 at 01:27:50PM -0500, Joe Btfsplk wrote:
>> Hardware acceleration is unchecked by default it Torbrowser.
>>
>> Other than some machines might not support it, is there a reason not
>> to enabled it?
>>
>> Some fingerprinting or other issue?
> https://trac.torproject.org/projects/tor/ticket/10531
> which points to
> https://lists.torproject.org/pipermail/tor-talk/2013-June/thread.html#28620
>
> Basically, some Windows systems were crashing when Tor Browser had
> hardware acceleration enabled.
>
> I think we made that change in TBB 3.5rc1:
> https://blog.torproject.org/blog/tor-browser-bundle-35rc1-released
>
> See the (alas not labelled with a ticket number) line:
> "Misc Prefs: Disable layer acceleration to avoid crashes on Windows"
>
> It looks from the various tickets like the issue is not entirely sorted
> for all users.
>
Thanks.  Has it been determined whether hardware acceleration being 
enabled can be detected for fingerprinting purposes?
I've had no TB crashes in Windows, but I'm also not sure there's any 
performance increase for typical internet usage in TB, whether hardware 
acceleration is / is not enabled.
>
> Be careful! I think you asked here about hardware acceleration in Tor
> Browser, aka our Firefox fork, but the man page you're quoting is for
> the program called tor.
>
Yes - missed that in my haste.
-- 
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

