On 4/14/07, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote:
Francis Moreau <francis.moro@xxxxxxxxx> wrote: > > hmm yes indeed it should do the job, but I don't see how you do that. > For example, let say I want to use "aes-foo" with eCryptfs. I can give > a higher priority to "aes-foo" than "aes" one. When eCryptfs asks for > a aes cipher it will pass "aes" name and since "aes-foo" has a higher > priority then the cypto core will return "aes-foo" cipher, right ? But > in this scheme, eCryptfs has not a higher priority than other kernel > users. How can I prevent others to use "aes-foo" ? You would assign "aes-foo" a lower priority and then tell eCryptfs to use "aes-foo" instead of "aes".
ok but do you think it's safe to assume that no others parts of the kernel will request "aes-foo" ? Remember that the main point is to optimize "aes-foo" ? I would say that it would be better if "aes-foo" could raise a flag for example indicating to the crypto core that this algo can be instatiate only one time... thanks -- Francis - 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
