On Tuesday, July 08, 2014 at 10:07:16 AM, Dmitry Kasatkin wrote:
[...]
quoted
Right, but my concern is not about unloading the kernel module, but
about the IMA module parameters left initialized. The existing code
will continue using ahash (software version), even though the kernel
module was unloaded, not shash. My question is about the software
implementations of ahash vs. shash performance.
Mimi
If HW driver will not be available, ahash loads generic driver which is
using shash.
Performance of that will be the same as for using shash directly.
Hi Dmitry, I think Mimi is concerned about the crypto accelerator dying mid-
flight.
Imagine a situation where you have a hardware crypto accelerator connected via
USB. You happily use IMA with this setup for days and then someone comes around
and pulls the USB cable out. Will this be able to cope with such situation, for
example by switching to software operations or such in some sane way ?
I presume that's the concern here.
Best regards,
Marek Vasut