On Wed, Aug 23, 2017 at 11:14:54AM +1000, teor wrote:
On 22 Aug 2017, at 16:22, Roman Mamedov wrote:
Hello,
Today I found that it is possible to force OpenSSL enable the use of CPU AES
acceleration even if it doesn't detect the "aes" CPU flag.
This would be a great addition to tor/doc/TUNI
nusenu wrote:
> Roman Mamedov:
> > But what if you need to
> > force-enable it. Turns out the syntax working for that is simply:
> >
> > OPENSSL_ia32cap="+0x202"
>
>
> Do you know what platforms and openssl versions support this?
>
And is the same available for libressl, which
Roman Mamedov:
> But what if you need to
> force-enable it. Turns out the syntax working for that is simply:
>
> OPENSSL_ia32cap="+0x202"
Do you know what platforms and openssl versions support this?
thanks,
nusenu
--
https://mastodon.social/@nusenu
https://twitter.com/nusenu_
> On 22 Aug 2017, at 16:22, Roman Mamedov wrote:
>
> Hello,
>
> Today I found that it is possible to force OpenSSL enable the use of CPU AES
> acceleration even if it doesn't detect the "aes" CPU flag.
This would be a great addition to tor/doc/TUNING.
Does someone want to summarise it and sub
Hello,
Today I found that it is possible to force OpenSSL enable the use of CPU AES
acceleration even if it doesn't detect the "aes" CPU flag.
Many VPS hosts configure their hypervisors in a way that does not have the
flag passed through into VPSes, even though all their host nodes surely have
CP
