Confirmed: openssl is using x86 crypto even with "-engine padlock", both in latest upstream and in the current hardy packages.
If I interrupt a debug build of openssl while running "openssl speed aes-128-cbc -engnie padlock" on a C3 gdb generally reports that it's been interrupted in:
_x86_AES_encrypt () at ax86-elf.s:55
The engine loads fine, and "openssl engine padlock" confirms it's detecting hardware support, but for some reason it's not actually using it.
Confirmed: openssl is using x86 crypto even with "-engine padlock", both in latest upstream and in the current hardy packages.
If I interrupt a debug build of openssl while running "openssl speed aes-128-cbc -engnie padlock" on a C3 gdb generally reports that it's been interrupted in:
_x86_AES_encrypt () at ax86-elf.s:55
The engine loads fine, and "openssl engine padlock" confirms it's detecting hardware support, but for some reason it's not actually using it.