Delivery-Date: Sat, 03 Jan 2015 08:36:39 -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 6A6921E022E
	for <archiver@seul.org>; Sat,  3 Jan 2015 08:36:38 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9F97C32EF6;
	Sat,  3 Jan 2015 13:36:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id DBE053273C;
 Sat,  3 Jan 2015 13:36:10 +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 bYzfYm8fNxqH; Sat,  3 Jan 2015 13:36:10 +0000 (UTC)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com
 [IPv6:2607:f8b0:4001:c05::22a])
 (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 B4E0F325DF;
 Sat,  3 Jan 2015 13:36:10 +0000 (UTC)
Received: by mail-ig0-f170.google.com with SMTP id r2so1391034igi.3;
 Sat, 03 Jan 2015 05:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:from:date:message-id
 :subject:to:cc:content-type;
 bh=1Wc9NAKxazyOznlIxDQx7y7pIJnu+OYIW5WT0Wn7xAk=;
 b=gM8iddFo5Wo18TZeB76RyWB9zpmPFSGH+1arKNnVV4++87DnkOxPJxX6WSCJ5N6eHg
 werGEZwfV5CgugChYIatzaiLPCKEv/+QyrXL2dJYd5XALTkD/csZ7I0I93FxzAx+/vdp
 UJfAIjQsFb+pHOlAMQTm9xfQalU+b1SG+rXMDsFMINm8V7TvGrUpBS158HMWPZ4kONaL
 A5jqAOKE/XrCiLL5Nq1E6jlrcjVAwYRISO6JJPyfeWwHoBMA8abSbm9M7/qIPKadTu5w
 0OMWXO+YBjV0AtGeNLQ3uEwfVH01XVf0D71avFXC8mf6LaEKBwsuAyPL1aCiq2uONzEm
 leFg==
X-Received: by 10.42.212.10 with SMTP id gq10mr60548492icb.79.1420292168451;
 Sat, 03 Jan 2015 05:36:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.167.6 with HTTP; Sat, 3 Jan 2015 05:35:28 -0800 (PST)
In-Reply-To: <CAJVRA1QOa3kZgCnC_=b_LFm6uX_Ofj48mAuofE5wpmqg_sxdBQ@mail.gmail.com>
References: <CAOmikWHB8yhfvHNh0ZW-d51zKbswZ_-6awgFvLR0dEB+OKvOBA@mail.gmail.com>
 <CAJVRA1QOa3kZgCnC_=b_LFm6uX_Ofj48mAuofE5wpmqg_sxdBQ@mail.gmail.com>
From: usprey <usprey@gmail.com>
Date: Sat, 3 Jan 2015 14:35:28 +0100
X-Google-Sender-Auth: BPIVclXmaBWZOgM67v7lXsIEf9g
Message-ID: <CAOmikWFjUUxVU9cBDH5RGbnRKaLyUvu1-dWzz-zGcUBeNYFLBw@mail.gmail.com>
To: tor-relays@lists.torproject.org
Cc: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] [tor-relays]  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 3 January 2015 at 13:34, coderman <coderman@gmail.com> wrote:
> 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 ;)
>

I will be glad to, but will have to know what to write first. =)

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

ty, will research further.

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

k, ty very much sir! =)

> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- 
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

