Hi YES (like in OCF and in the current cryptoAPI)
Sounds good to me, When is this Async Crypto API, going to be ready?? Since I'm planning to take a full month vacation, by the end of this week, and if by the time I will be back, this Async Crypto APIs will be ready, and _part_of_the_mainline_, then I will need to re-evaluate my decision for going with the OCF, since the "big guys here likes to go with the mainline". Regards Ronen Shitrit Marvell Semiconductor Israel Ltd -----Original Message----- From: Herbert Xu [mailto:[EMAIL PROTECTED] Sent: Monday, September 05, 2005 5:39 AM To: Ronen Shitrit Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; linux-crypto@vger.kernel.org Subject: Re: OCF or Acrypto for IPSec and dm-crypt Ronen Shitrit <[EMAIL PROTECTED]> wrote: > > I think, Correct me if I'm wrong, > What you described below, is 1 session with few operations (using the > routing feature of the acrypto), but once the session/set of > operations are done, then the session is closed. I see. You want the session to last through the lifetime of an IPsec SA, right? Well the good news is that the Async Crypto API that I'm working on will do exactly that. The session is identified with the existing crypto_tfm object which is tied to each IPsec SA (for IPsec that is). 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
