Jivin Ronen Shitrit lays it down ...
>
> Hi
>
> I'm using the OCF package,
> I compiled the OpenSSL package with the OCF patch.
> I also compiled the OCF as kernel module with SW crypto.
> I ran the speed test from the OpenSSL and everything seems to work nice.
>
> When I looked into the speed test, I figured that if an application want
> to use the OpenSSL with the OCF crypto dev engine, then it must specify
> it, and the APIs are different then when using the integrated SW crypto
> inside the Open SLL.
>
> I want to use the Rsync application which uses the OpenSSL lib, in a way
> that it will use the OCF interface by default.
> Should I change the Rsync Application??
> Is there any patch which cause the OpenSSL to use the OCF crypto dev
> engine by default (if possible) and if not then Go to the other engines
> or the OpenSSL integrated SW crypto??
> Any other suggestions??
It's something I have wondered about myself.
Have a look at the ssh.patch with OCF, it may give you some hints as to
what is needed in rsync.
Basically you need to call:
ENGINE_load_builtin_engines();
ENGINE_register_all_complete();
near the start of the program. What I don't know for sure is how to
ensure the HW engines take precedence over the software ones :-(
With scp I could do it by choosing appropriate alg's IIRC, it's been a
while,
Cheers,
Davidm
--
David McCullough, [EMAIL PROTECTED], Custom Embedded Solutions + Security
Ph:+61 734352815 Fx:+61 738913630 http://www.uCdot.org http://www.cyberguard.com
-
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
