On Fri, May 20, 2016 at 10:50:38AM -0500, Gary R Hook wrote: > > Why is (or should) setting geniv (be) required? > > crypto_givcipher_default() appears to call crypto_default_geniv() if > the geniv member > is NULL. That function returns "eseqiv" or "chainiv" (under certain > conditions). If an > implementation isn't generating its own IVs, shouldn't the default > happen anyway? Or is > this more a matter of populating the structure with known, > intentional values? > > Thank you for any illumination provided.
In the upstream kernel AEAD geniv has been completely phased out and no longer exists. Denis is working on an old kernel that still has it. We haven't yet phased it out for skcipher but I'm working on it. Cheers, -- Email: Herbert Xu <herb...@gondor.apana.org.au> 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
