public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/4] Tor: Use crypto hardware acceleration if available
Date: Mon, 27 Sep 2021 19:46:50 +0100	[thread overview]
Message-ID: <5438800B-3D00-4F77-9359-99332D90E85B@ipfire.org> (raw)
In-Reply-To: <37079e43-a5af-db04-086e-750f04151b75@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

Hello,

Can you elaborate a little bit more on this?

Tor is using OpenSSL which by default should use RDRAND, AES-NI (if applicable) and so on.

What does this option change?

-Michael

> On 25 Sep 2021, at 08:08, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> html/cgi-bin/tor.cgi | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/html/cgi-bin/tor.cgi b/html/cgi-bin/tor.cgi
> index ce579aec1..2b0d93336 100644
> --- a/html/cgi-bin/tor.cgi
> +++ b/html/cgi-bin/tor.cgi
> @@ -731,6 +731,7 @@ sub BuildConfiguration() {
> 
> 	# Global settings.
> 	print FILE "Sandbox 1\n";
> +	print FILE "HardwareAccel 1\n";
> 	print FILE "ControlPort $TOR_CONTROL_PORT\n";
> 
> 	if ($settings{'TOR_ENABLED'} eq 'on') {
> -- 
> 2.26.2


  parent reply	other threads:[~2021-09-27 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25  7:07 [PATCH 1/4] Tor: Enable syscall sandbox Peter Müller
2021-09-25  7:08 ` [PATCH 2/4] Tor: Use crypto hardware acceleration if available Peter Müller
2021-09-25  7:08   ` [PATCH 3/4] Tor: Do not try to support IPv6 for Directory and OR ports Peter Müller
2021-09-25  7:09     ` [PATCH 4/4] Tor: Bump package version Peter Müller
2021-09-27 18:46   ` Michael Tremer [this message]
2021-10-04 10:49     ` [PATCH 2/4] Tor: Use crypto hardware acceleration if available Peter Müller
2021-10-04 13:59       ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5438800B-3D00-4F77-9359-99332D90E85B@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox