On Tue, Jul 06, 2010, Ger Hobbelt wrote: > On Tue, Jul 6, 2010 at 9:10 AM, Deckers, Rob <rob.deck...@oce.com> wrote: > > > If you look in the OpenSSL code (of between the .lib files after build) > > , you will find 11 so called engines. > > - Sureware > > - Padlock > > - Cswift > > - 4758cca > > - Aep > > - Atalla > > - Capi > > - Chil > > - Nuron > > - Gmp > > - Ubsec > > > > Does anyone know if these are in the Libeay32.dll of in the Ssleay32.dll > > ? > > > > > Neither. Engines can be considered as crypto 'plugins' and when you look at > the makefile (engines/Makefile) you'll see that each engine is made to be > its own .so dynamic loadable lib (...<engine>_eay32.dll under cygwin). The > application can set up OpenSSL to load and use the engine(s) of choice; for > each engine there's an ENGINE_load_<engine>() API, which performs a so/dll > dynlibrary load at run time under the hood through the bind_helper() > function (see the various engines source code). >
Just a quick additional bit of info. Although they aren't linked into libeay32.dll in the default build the option "enable-static-engine" can be set at Configure time to link them in. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
