[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4008 [Tor Relay]: Identify safe, common, useful openssl engines to enable by default
#4008: Identify safe, common, useful openssl engines to enable by default
-----------------------------+----------------------------------------------
Reporter: nickm | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor Relay | Version:
Keywords: crypto, openssl | Parent:
Points: | Actualpoints:
-----------------------------+----------------------------------------------
Comment(by nickm):
Replying to [comment:1 tmpname0901]:
> Which engines have been tried and found to be crash-prone? Which have
not yet been tried?
At this point, it's been a few years; I'd have to look it up.
> A related quick-fix is to provide 64-bit Windows executables. (I'm
assuming that most users in Unix environments build their own Tor
binaries.)
>
> The OpenSSL crypto code is just plain faster when built for a 64-bit CPU
(relative to the same CPU running a 32-bit binary), and 64-bit Windows
systems are no longer a rarity. The cost in local system responsiveness
while running a Tor relay on Windows would be greatly reduced by simply
doing a 64-bit build of the same code that's being built now.
This is worth opening a new ticket for. This is not a general "Make our
crypto faster" ticket.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4008#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs