On Wed, May 02, 2007 at 02:57:21PM +1000, Herbert Xu ([EMAIL PROTECTED]) wrote: > > For example HIFH adapter can not perform blowfish encryption, but it > > will be requested to do so each time new tfm is being requested, if my > > analysis correct... > > Sorry, I think I've misled you there. For something like the HIFH > adapter you wouldn't do a template at all (well, not until we start > expressing supported key lengths through templates). > > You'd simply register an algorithm of type BLKCIPHER | CRYPTO_ALG_ASYNC > for each algorithm that you support. You'd set the name of each of these > according to their algorithm. So for example AES would just be registered > as "aes" (of course, you'd set your driver name differently).
I.e. do not use uncommented^Wencrypted cryptd source, but just write a driver with couple of algorithms with magic CRYPTO_ALG_ASYNC bit set in its flags? That would be much simpler. I will start from that point, thans Herbert. > 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 -- Evgeniy Polyakov - 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
