Dimitrios Siganos <dimitris@xxxxxxxxxxx> wrote: > After sending the email, I realised what's happening... > crypto_cipher_setkey seems to be used that way only when a child cipher > is used by another (parent) cipher as a way to delegate work. > > It seems that crypto_cipher_setkey accepts a number of request flags > CRYPTO_TFM_REQ_* which must be passed to the child object and after > completion of crypto_cipher_setkey, it returns some results flags > CRYPTO_TFM_RES_* back which must be passed to the parent object. > > So the flag manipulation before and after is because we are using an > internal cipher object to delegate the work. You're absolutely correct. Feel free to send patches to add comments too. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <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
