Hi Michal: On Thu, May 25, 2006 at 09:27:20AM +1200, Michal Ludvig wrote: > > It's not a rocket science. It does, however, introduce backward > incompatibility. But I don't think that would be a problem - it's a > module only for testing anyway.
I like the concept. But I think you should be more audacious :) How about making tcrypt modularised? What I'd like to see is a model where each crypto algorithm can provide its own test vectors that produces its own module. For instance, to test AES I'd do something like 'modprobe aes-tcrypt <params>'. This way we will no longer have the ever growing tcrypt.[ch] that are starting to look scary. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
