Hi, I notice that the crypto in the kernel dynamically loads in crypto modules.
It appears that crypto algorithms are loaded first followed by cbc.ko, then crypto_blkcipher.ko and authenc. How does crypto decide which modules to load. It seems related to the string "authenc(hmac(sha1),cbc(aes))" ? Thanks for any info. Regards, Dean Jenkins MontaVista Software -- 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
