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
On Tue, Dec 19, 2006 at 11:51:01AM +0100, Andreas Jellinghaus ([EMAIL
PROTECTED]) wrote:
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
On Mon, Dec 18, 2006 at 08:38:54AM +0100, Andreas Jellinghaus ([EMAIL
PROTECTED]) wrote:
Does acrypto still have the same size restrictions
I ran into with the last release?
Actually I do not recall what is 'size retrictions' - if you talk about
possibility to use software crypto provider,
On Mon, Dec 18, 2006 at 02:00:26PM +0100, Andreas Jellinghaus ([EMAIL
PROTECTED]) wrote:
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
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
Hello.
I am pleased to announce new release of the acrypto for 2.6.19 kernel -
first asynchronous crypto layer for Linux kernel 2.6.
Acrypto allows to handle crypto requests asynchronously in hardware.
Acrypto supports following features:
* multiple asynchronous crypto device queues
* crypto
