Re: [Ocf-linux-users] Via Padlock?
Brought to you by:
david-m
From: Albert L. <alb...@gm...> - 2007-09-26 16:09:31
|
I got it to work. For some reason when I compiled openssl, I didn't have the cryptodev.h header in the right place (figured that out compiling the cryptotest tool). The results are again great, but openssl is faster when it uses the padlock driver directly: http://www.docunext.com/resources/mediawiki/index.php/Via_Padlock_OCF-Linux_Integration On 9/26/07, David McCullough <Dav...@se...> wrote: > > Jivin Albert Lash lays it down ... > > I was also wondering if there was any consideration of adding a via > > padlock driver for ocf-linux. Unlike the geode-aes module, the > > padlock-aes doesn't seem to make itself available to the cryptoAPI. > > Hmm, I have used the padlock via cryptoapi for openswan (without OCF). > I would have thought it should work with cryptosoft as well. > > openssl also has a padlock engine as well. > > Checkout > > http://www.logix.cz/michal/devel/padlock/ > > for more info, > > Cheers, > Davidm > > -- > David McCullough, dav...@se..., Ph:+61 734352815 > Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com > -- My Blogs: http://www.docunext.com/ http://www.albertlash.com/ |