Delivery-Date: Fri, 27 Jun 2014 16:42:13 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 00CB71E0BC2
	for <archiver@seul.org>; Fri, 27 Jun 2014 16:42:11 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8A2562E7D1;
	Fri, 27 Jun 2014 20:42:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3B5F82DC61
 for <tor-talk@lists.torproject.org>; Fri, 27 Jun 2014 20:41:44 +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 BIAbyLWOTr56 for <tor-talk@lists.torproject.org>;
 Fri, 27 Jun 2014 20:41:44 +0000 (UTC)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com
 [IPv6:2607:f8b0:400d:c04::22c])
 (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 0F9ED2C085
 for <tor-talk@lists.torproject.org>; Fri, 27 Jun 2014 20:41:44 +0000 (UTC)
Received: by mail-qg0-f44.google.com with SMTP id j107so4859132qga.17
 for <tor-talk@lists.torproject.org>; Fri, 27 Jun 2014 13:41:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=h5MQ0hTtYkLNBpnpkt/5pKjaQ1iCMeaw1l1vUHQORCE=;
 b=Hticyjd/qAhbgl5fdtXW58BvtkjWu0lfkJ391tb8DpboFB7teFBF+i3xJsqM7zbmYX
 N6gNblbEEaq0LvvSd5k6/lATRaZAHXjwC4aYEMR4BjNawzgBZa4U/P7WXgBTFYaCVe/R
 tMh/tt25c2D+LYcjfWxVptsNXUSGIiVC2UZ3iKYxZUXUbWGnRg3WkzRbxG5uG0gUYmwp
 e1Jg9MkNyp/uOccOTIipxD/DGnW58xmzvZ4jh5xQG4x5AXNLxIKHMRDFSex1na7AmFCt
 FtzFj5g2NSgS3vbyxVkMpyFb2zzYhLcm+fndmPjttnFzORloD5To5sPEd/DEeBJ7qKpe
 gsLQ==
MIME-Version: 1.0
X-Received: by 10.140.80.49 with SMTP id b46mr34568181qgd.102.1403901700927;
 Fri, 27 Jun 2014 13:41:40 -0700 (PDT)
Received: by 10.96.179.232 with HTTP; Fri, 27 Jun 2014 13:41:40 -0700 (PDT)
In-Reply-To: <53ADB7A6.7080709@gmx.com>
References: <53ADB7A6.7080709@gmx.com>
Date: Fri, 27 Jun 2014 13:41:40 -0700
Message-ID: <CAJVRA1Qxjt4zqnqpoJcQuSiDNa9run=5ULTzo9s=YrV=WCeGuQ@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org
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-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>

On Fri, Jun 27, 2014 at 11:27 AM, Joe Btfsplk <joebtfsplk@gmx.com> 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?

the only reason you may have wanted to not enabled hardware
acceleration was fixed last year. (openssl was inadvertently forcing
use of a single entropy source (RDRAND) when default engines enabled
in a specific first Tor run sequence. (see
https://trac.torproject.org/projects/tor/ticket/10402 )

there used to be some engines that were slower than optimized CPU asm
variants, but i don't believe these are in use any more.

please enable this option, especially if you've got a recent VIA or
Intel processor.


best regards,
-- 
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

