On Wed, Jun 03, 2009 at 07:40:50PM +1000, Herbert Xu wrote: > > I see. How about if we let tcrypt test algorithms by name, e.g., > something like > > modprobe tcrypt alg='pcrypt(authenc(hmac(sha1),cbc(aes))' >
I'm not that sure whether this does what I want. If pcrypt has cra_name = pcrypt(authenc(hmac(sha1),cbc(aes))) this would instatiate this algorithm, but esp wants an algorithm with cra_name = authenc(hmac(sha1),cbc(aes)). These names are not matching, so __crypto_alg_lookup() will not choose for the pcrypt version regardless of the higher priority. Setting cra_name = authenc(hmac(sha1),cbc(aes)) for pcrypt seems to be not possible too, because pcrypt needs authenc as an underlain algorithm and the system will not load two aead algorithms with the same name. This was one of the reasons why I added a wrapper to authenc that is instantiated along with authenc. Is this the case or do I miss something? -- 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
