Jivin Ronen Shitrit lays it down ... > Hi > > From the OpenSSL documentation: > (http://www.openssl.org/docs/crypto/evp.html# > http://www.openssl.org/docs/crypto/engine.html# ) > > "The fact that ENGINEs are made visible to OpenSSL (and thus are linked > into the program and loaded into memory at run-time) does not mean they > are ``registered'' or called into use by OpenSSL automatically - that > behavior is something for the application to control. Some applications > will want to allow the user to specify exactly which ENGINE they want > used if any is to be used at all. Others may prefer to load all support > and have OpenSSL automatically use at run-time any ENGINE that is able > to successfully initialize - i.e. to assume that this corresponds to > acceleration hardware attached to the machine or some such thing." > "If ENGINE implementations of ciphers or digests are registered as > defaults, then the various EVP functions will automatically use those > implementations automatically in preference to built in software > implementations." > > Specific for the rsync: > The rsync uses the OpenVPN, which uses the OpenSSL engine by registering > all available engines.
Have you tried it yet, it would be nice to know if it works in practice :-) 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
