By applying the cryptodev patch in openssl, all the
applications that use openssl (postfix, tomcat etc) are automatically
executed at hardware.
As far as it concerns the openssl speed, we can avoid
the hardware acceleration by using the evp parameter.
My wonder is how we can avoid the hardware acceleration
from application side?
Is there an engine name that we can use to run the
application at software?
the fact that 'openssl engine -t' shows an engine as "available" does
not mean that it is automagically *used*; on my openssl 1.0.1e build I
see 'rsax' and 'gost' as available engines but I am quite certain that
they are not used unless I specify them on the command line OR if I
load them in my code using something like