On Tue, May 13, 2008 at 04:35:03PM -0400, Mikulas Patocka wrote:
>
> And where would you propose to place this bit?
>
> One possibility would be struct crypto_tfm->crt_flags
> Another possibility is struct crypto_alg->cra_flags
The latter definitely because this is an algorithm property.
> Can c
Hi Herbert,
I am re-sending this email as I don't believe it got to the mailing
list. Due to email problem, I am forward this patch on behalf of Shasi
Pulijala who worked on this user space interface for Linux CryptoAPI.
This should add support for OpenSSL. Please note that user of this patch
must
On Tue, 13 May 2008, Herbert Xu wrote:
On Mon, May 12, 2008 at 11:28:44PM -0400, Mikulas Patocka wrote:
Or do you thint it would be useless (all major disk-encryption algorithms
read input buffer more times?) or it would create too much code
complexity?
I'm open to this approach. As long
Hi,
Patch 2/3 attached. I still can't get the line wrap problem solved.
Therefore it is attached instead inline.
-Loc
0002-CRYPTO-cryptd-Add-asynchronous-hash-support.patch
Description: 0002-CRYPTO-cryptd-Add-asynchronous-hash-support.patch
Hi,
Patch 3/3 attached. I still can't get the line wrap problem solved.
Therefore it is attached instead inline.
-Loc
0003-CRYPTO-tcrypt-Add-asynchronous-hash-support.patch
Description: 0003-CRYPTO-tcrypt-Add-asynchronous-hash-support.patch
Hi,
Patch 1/3 attached. I still can't get the line wrap problem solved.
Therefore it is attached instead inline.
Please note:
1. ahash_request has an extra variable 'void *info' for future uses with
KASUMI
2. Any particular reason for removing ahash_nosetkey from function
crypto_init_ahash_ops -
