So why doesn't aes.c use the same thing as is initialized in crypto.c?
It would seem that this is always the right thing to do, and that
because we don't do it acceleration only works for some uses of AES.
The fix seems to be to change aes.c's use of defines to match that in
crypto.c.
Sincerely,
Following the instructions in the Configure Thunderbird to work through
Tor help file. I've successfully set up tormail in Thunderbird.
However, I don't know what the No Proxy for field on the TB Network
Disk Space Settings tab is supposed to mean. Whether I leave
Localhost, 127.0.0.1 (as
On Nov 20, 2011 8:47 AM, Watson Ladd watsonbl...@gmail.com wrote:
So why doesn't aes.c use the same thing as is initialized in crypto.c?
Because, according to our benchmarks, on systems *without* aesni or
other hardware acceleration, using the AES_* functions is actually
faster than the EVP_*
On 11/20/2011 7:21 PM, eliaz wrote:
Following the instructions in the Configure Thunderbird to work
through Tor help file. I've successfully set up tormail in
Thunderbird. However, I don't know what the No Proxy for field on
the TB Network Disk Space Settings tab is supposed to mean.
