<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks Yawning,<br>
<br>
I was trying to make due with the equipment I had laying around,
but, anyways, I did learn a bit along the way. Thanks for your
input.<br>
<br>
<div class="moz-cite-prefix">On 3.5.15 0:40, Yawning Angel wrote:<br>
</div>
<blockquote cite="mid:20150503044049.485e4c23@schwanenlied.me"
type="cite">
<pre wrap="">On Sat, 02 May 2015 12:10:33 -0400
12xBTM <a class="moz-txt-link-rfc2396E" href="mailto:12xbtm@gmail.com"><12xbtm@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">So, I deleted the /usr/local/ssl/ folder and went from there. I got
the sudo make test going again, and it failed D: . So the last thing
remains: How do I get/install that patch that supposedly corrects
this?
</pre>
</blockquote>
<pre wrap="">
...
Quoting from the README file:
</pre>
<blockquote type="cite">
<pre wrap="">Note that OpenSSL's cryptodev implementation is outdated, and there
are issues with it. For that we recommend to use the patches
below, that we have provided to the openssl project.
<a class="moz-txt-link-freetext" href="http://">http://</a>...
</pre>
</blockquote>
<pre wrap="">
You're making it sound as if the patches are on display in the bottom
of a locked filing cabinet stuck in a disused lavatory with a sign on
the door saying 'Beware of the Leopard'.
Anyway...
* I haven't bothered to check if the patches apply cleanly, only that
they weren't ever merged. Shouldn't be that hard to fix the patches
if they've rotted.
* According to one of the writeups linked, in 2013 cryptdev wasn't
exposing a CTR-AES EVP engine. If this is still the case, the bulk
of tor's AES calls will not benefit from the acceleration (Skimming
the cryptdev code quickly, this would ultimately be a kernel issue).
* The SHA acceleration will only help TLS, because the bulk of the
SHA calls in tor don't use the EVP interface (For good reasons in
the case of SHA1, and "it's a good idea, someone should do it"
reasons for SHA256).
I'd expect in a lot of cases that the gains would be fairly minimal
anyway, since using hardware acceleration with this configuration
requires a syscall.
</pre>
<blockquote type="cite">
<pre wrap="">if there's a better way to go about having HW-accelerated crypto for
Tor (excluding Intel aes-ni), please let me know.
</pre>
</blockquote>
<pre wrap="">
Instead of some garbage TI part, use something that supports ARM-v8's
AES, SHA1, SHA256, and VMULL instructions.
Regards,
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tor-relays mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a>
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
</pre>
</blockquote>
<br>
</body>
</html>