On Wed, Jun 03, 2009 at 11:32:16AM +0200, Steffen Klassert wrote: > > > So what I suggest is that you make pcrypt take a higher priority > > for now, so that it always is the default once instantiated. > > After all if you instantiate it then you probably want to use it > > as the default. > > Yes, in fact the instantiating is my problem. E.g. esp asks for an > authenc(...,...) algorithm, so the crypto manager tries to instantiate > a template with name authenc. If I don't want to touch the network > subsystem I can't change the name to pcrypt(authenc(...,...)) easy. > So one solution was to add a default wrapper template arround authenc > that will be instantiated along with authenc. 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))' which would simply call crypto_has_alg on the string alg? That should instantiate alg, and test it too if there are vectors. This is a new interface too, but at least it pretends to be generic :) Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
