status of async crypto
Hi all Until recently I was using kernel 2.6.12 with the OCF package in order to get async encryption with HW engine for OpenSWAN, dm-crypt and OpenSSL. Lately I have decided its time to move on to the latest kernel, and I found that there is a new async crypto support in the kernel :) Now I have to decide whether to use the OCF or the native async crypto. I have some questions and I would really appreciate if you can help here: I saw that the current code support async crypto for the dm-crypt, does it also support async crypto for the klips? Is there any support for using the async crypto from the OpenSSL engine library? I saw that the async crypto support block cipher, does it also support digest operations? Can it support encryption + authentication (lets say AES-SHA1) as one operation? Is there any Documentation available? (I guess not) What is the todo list for further development of the async crypto support? Thanks for your advice Ronen Shitrit - 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
Re: status of async crypto
On Sun, Aug 05, 2007 at 01:50:48PM +0300, Ronen Shitrit ([EMAIL PROTECTED]) wrote: I saw that the current code support async crypto for the dm-crypt, does it also support async crypto for the klips? Is there any support for using the async crypto from the OpenSSL engine library? I saw that the async crypto support block cipher, does it also support digest operations? Can it support encryption + authentication (lets say AES-SHA1) as one operation? Is there any Documentation available? (I guess not) No for all above. What is the todo list for further development of the async crypto support? New drivers and extending functionality if required. Some work is being done in this area, although not that fast. -- 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
