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). -- Met vriendelijke groeten / Best regards, Ger Hobbelt -------------------------------------------------- web: http://www.hobbelt.com/ http://www.hebbut.net/ mail: g...@hobbelt.com mobile: +31-6-11 120 978 --------------------------------------------------
