Delivery-Date: Sat, 03 Jan 2015 07:34:58 -0500
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,
	URIBL_BLOCKED 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 E57771E030B
	for <archiver@seul.org>; Sat,  3 Jan 2015 07:34:56 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 42C9832E80;
	Sat,  3 Jan 2015 12:34:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1009832E55;
 Sat,  3 Jan 2015 12:34:29 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 DeTPXNEismPz; Sat,  3 Jan 2015 12:34:29 +0000 (UTC)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com
 [IPv6:2a00:1450:4010:c03::22e])
 (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 AC1AE32E45;
 Sat,  3 Jan 2015 12:34:28 +0000 (UTC)
Received: by mail-la0-f46.google.com with SMTP id q1so16214749lam.5;
 Sat, 03 Jan 2015 04:34:25 -0800 (PST)
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
 :cc:content-type;
 bh=Wzo4y0tdtGouOjuSuUK3wyDj2hMD0Ra9Z9rVDhWoQEE=;
 b=uDCd+iu2GWqqlL5bbQTICZgOF06GcRLcJgSrwBb9WE5iHuYrtsJK+4uSNeagINvs0N
 Xvb7XlpN0AnBFIlpDHPNvpgetp0ZhcxR8TpnbKgopOpoq25FMoccttKvWuIqNhaO3SaS
 eLNONH3xlBcmQS42p4tHtXs49yuLMOOwRiw2t03K0S5jLlwK00wR9e9MSw1Leb6Ed0lu
 NAJTh26FaM1PWE8i5PTHk2/2ih+WxnqJNATPAHFoezmBwhrRcL8nxwWrRjW0VTgXrqjh
 nU5Q2z/Eb3uiU4d6hV8F0Xhvt9zmf4NOLI7OEZA+q+J5ndSsldxgh9wDyuN7gcbB9tm8
 bROQ==
MIME-Version: 1.0
X-Received: by 10.152.7.206 with SMTP id l14mr81530229laa.1.1420288465546;
 Sat, 03 Jan 2015 04:34:25 -0800 (PST)
Received: by 10.25.157.202 with HTTP; Sat, 3 Jan 2015 04:34:25 -0800 (PST)
In-Reply-To: <CAOmikWHB8yhfvHNh0ZW-d51zKbswZ_-6awgFvLR0dEB+OKvOBA@mail.gmail.com>
References: <CAOmikWHB8yhfvHNh0ZW-d51zKbswZ_-6awgFvLR0dEB+OKvOBA@mail.gmail.com>
Date: Sat, 3 Jan 2015 04:34:25 -0800
Message-ID: <CAJVRA1QOa3kZgCnC_=b_LFm6uX_Ofj48mAuofE5wpmqg_sxdBQ@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org
Cc: tor-relays@lists.torproject.org
Subject: Re: [tor-talk] HardwareAccel: Current proper use???
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 1/3/15, usprey <usprey@gmail.com> wrote:
> Summary:
> The documentation is still somewhat vague on the best use of the
> "HardwareAccel" option.


you could submit a patch ;)



>> *HardwareAccel* *0*|*1*
>>
>> If non-zero, try to use built-in (static) crypto hardware acceleration
>> when available. (Default: 0)

in OpenSSL land, there are two types of crypto offload / hw engines:
 built-in (static), and dynamically loaded (dynamic).

the "HardwareAccel 1" option says to enable the built-in / static
engines.  you may have a patched OpenSSL that will automatically try
dynamic engines without explicitly attempting to load them by name (as
libengine.so dlopen'ed implementations).



> https://www.torservers.net/wiki/setup/server#aes-ni_crypto_acceleration
> claims
> no intervention is needed in regards of aes-ni accelaration, but I would
> like to add an explanation or source to this recommendation.

in some versions of OpenSSL, you will need to enable HardwareAccel
(but not use a dynamic engine - aesni is built-in / static).

you will need to consult the distribution of OpenSSL you are using to
be sure - it varies by version and pkg maintainers.



> Question_1:
> If my CPU supports and have loaded aesni_intel on linux with OpenSSL is
> 1.0.1.j-1, should I leave HardwareAccel off or explicitly enable it?

leave HardwareAccel 1, but do not bother with a dynamic named engine opt.
-- 
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

