On Mon, Aug 12, 2013 at 10:49:13AM -0300, Marcelo Cerri wrote: > > So does that means that it's possible to keep data in the tfm's context > that is the same for a single SA, such as the AES expanded key, but it's > not possible to keep data that is specific for the current operation, > such as an operation state that the driver might require? Correct. > Actually I think that probably I have misunderstood the blkcipher > interface, so here it is another question: is each encrypt/decrypt call > a complete operation? I mean, I'm considering that I could always chain > a series of calls to encrypt data in separated chunks, in a similar way > that is done for the hash interface and because that I'm assuming that I > would have to keep state between those calls if the device requires > that. You could always chain blkcipher operations together, however, the only state that can be stored is the IV. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
