Evgeniy Polyakov wrote:
You can change it in async_provider in compilation time or I can create
module version. There is an item in related todo list to use crypto
contexts, they were created exactly for such kind of things (actually
for hardware devices which do not support realtime key
Evgeniy Polyakov wrote:
Actually I do not recall what is 'size retrictions' - if you talk about
possibility to use software crypto provider, which supports one cipher
in a time, then yes, but it is intended to be used with hardware though.
Otherwise I do not recall any problems pointed to me.
Does acrypto still have the same size restrictions
I ran into with the last release?
Thanks, Andreas
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Evgeniy Polyakov wrote:
Hello.
I'm pleased to announce asynchronous crypto layer (acrypto) [1] release
for 2.6.18 kernel tree. Acrypto allows to handle crypto requests
asynchronously in hardware.
Combined patchset includes:
* acrypto core
* IPsec ESP4 port to acrypto
* dm-crypt port to
