Re: [PATCH 4/4] crypto: lmk2/lmk3 cipher block modes

Max Vozeler <[email protected]> Mon, 1 Feb 2010 11:32:27 +0100
Newsgroups gmane.linux.kernel.cryptoapi,gmane.linux.cryptography
Message-ID <[email protected]>
Hi Herbert,

On Tue, Jan 19, 2010 at 09:00:38PM +1300, Herbert Xu wrote:
> Let's keep lmk2/lmk3 as separate modes, but implement it as a
> wrapper around cbc.  That is, instead of allocating the cipher,
> you'd allocate "cbc(cipher)" (as an ablkcipher) and use it to
> perform the actual encryption/decryption.

I started looking at this today.

I'm wondering if I'm heading in the right direction since
this is stretching my understanding of the API:

Would it look something like ccm, in that

 alloc does
  - crypto_grab_skcipher(spawn, "cbc(aes)"
  - crypto_skcipher_spawn_alg()

 then my alg.cra_init does
  - crypto_spawn_skcipher ? 

Any advice appreciated. In the meantime I'll read the code
to get a better understanding of how this fits together.

	Max
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html