Please read the code, not only Tor's code, but also OpenSSL's code.
Yes, AES is not displayed as engine itself, however, it still does not seem to
use aes-ni instructions unless told to initialize engines via the code I
deducted.
If this proves anything, I ran an Exit Relay in 2013 before my ho
On 12/17/23 21:16, likogan via tor-relays wrote:
My exit relay has seen steadily decreasing traffic from 8MBps to 6MBps
over the span of three weeks. It averages a load of ~50% CPU usage and
~65% RAM usage. It's rated network capacity is 17Mbps on a 10GB link.
Why would traffic decrease if I hav
On Mon, 18 Dec 2023 16:57:37 +
George Hartley wrote:
> Please read the code, not only Tor's code, but also OpenSSL's code.
>
> Yes, AES is not displayed as engine itself, however, it still does not seem
> to use aes-ni instructions unless told to initialize engines via the code I
> deducted.
On Mon, 18 Dec 2023 15:58:52 +
George Hartley wrote:
> I had a quick look at the manual, and it stated:
>
> > HardwareAccel 0|1
>
> > If non-zero, try to use built-in (static) crypto hardware acceleration >
> > when available. Can not be changed while tor is running. (Default: 0)
>
> A qu
On Mon, 18 Dec 2023 10:03:01 +
George Hartley via tor-relays wrote:
> lscpu | grep aes
>
> If the command returns nothing, sadly your CPU does not support hardware AES
> acceleration, or if you run your OS in a VM, then the VM operator likely did
> not set "host" as CPU model.
>
> If howeve
Hello Likogan (you did not specify a name, so I just took your domain name).
First, lets look at issue number one:
If your Tor Exit is using ~50% of the entire CPU (VM or dedicated server?)
while only routing 6 Mbps, then you are likely not using hardware AES
acceleration (aesni).
For example,
