Hi! As indicated before, I'm spending some time on polishing Michal Ludvig's patches for the VIA PadLock PHE (SHA1/244/256 acceleration).
One of the remaining issues that were never addressed is to add some testing functionality to the patch, i.e. anyone building openssl can test the correct operation of the engine, just like test_padlock does for AES. So what I need to do is to execue the openssl program twice, once with software engine, another time with padlock engine. > openssl dgst -sha1 -engine padlock works just fine. However, since the "ENGINE_load_openssl()" statement is disabled in eng_all.c, I cannot force the openssl program to use the software implementation using the following commmand > openssl dgst -sha1 -engine openssl results in 'cannot open shared object file' error. So what is the correct way to ascertain the use of a pure software implementation as opposed to any hardware-accelerated engine? Just not use the '-engine' statement? But I guess in this case the default depends on the openssl configuration file, doesn't it? Thanks in advance, -- - Harald Welte <[EMAIL PROTECTED]> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
