You shouldn't need a separate library for the CAPI engine - it's built into the OpenSSL library itself. Since you have a build of OpenSSL that has CAPI built in, linking STunnel with it should suffice. If not, then that looks like a bug in STunnel (i.e., it's not loading the engine correctly).
Michael Wojcik Technology Specialist, Micro Focus From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Derek Cole Sent: Friday, 14 November, 2014 17:39 To: openssl-users@openssl.org Subject: Re: Compile 1.0.1j on Win8.1 with capi Just to add some more information - When I do my nmake -f ms\ntdll.mak command, I do end up with some out32dll.dbg and out32.dbg directories in my source folders, and if I browse to the out32.dbg folder and do "openssl engine" I do get some output: $ ../out32.dbg/openssl.exe engine (rdrand) Intel RDRAND engine (dynamic) Dynamic engine loading support (4758cca) IBM 4758 CCA hardware engine support (aep) Aep hardware engine support (atalla) Atalla hardware engine support (cswift) CryptoSwift hardware engine support (chil) CHIL hardware engine support (nuron) Nuron hardware engine support (sureware) SureWare hardware engine support (ubsec) UBSEC hardware engine support (padlock) VIA PadLock (no-RNG, no-ACE) (gost) Reference implementation of GOST engine (capi) CryptoAPI ENGINE So it seems to me like the libraries maybe are getting built, but I can't seem to link to them correctly in my stunnel code. And also, if i do the nmake -f ms\ntdll.mak install, *.lib files in the out32dll.dbg folder do not make it to the lib folder of my install directory. They are in there for the precompiled binaries. Were those just copied in by hand? On Fri, Nov 14, 2014 at 3:11 PM, Derek Cole <derek.c...@gmail.com<mailto:derek.c...@gmail.com>> wrote: Hello, I am noticing that when I install the OpenSSL bundle from http://slproweb.com/products/Win32OpenSSL.html The lib folder gets a lot of .lib files in it that are corresponding to the engines such as capi.lib How can I compile OpenSSL to generate those same lib files? Is it simply a matter of configuring with enable-capieng to make this happen? I need to generate the libraries for use in my stunnel compile that I am trying to do on windows. When I just did a build line like in the INSTALL.W32 : > perl Configure VC-WIN32 no-asm --prefix=c:/some/openssl/dir > ms\do_ms I do not get those same .lib files, specifically, the capi.lib file is missing, so I get a message like the following from stunnel when it's running: [ ] Enabling support for engine 'capi' [!] error queue: 2606A074: error:2606A074:engine routines:ENGINE_by_id:no such engine [!] error queue: 260B6084: error:260B6084:engine routines:DYNAMIC_LOAD:dso not found [!] error queue: 25070067: error:25070067:DSO support routines:DSO_load:could not load the shared library [!] ENGINE_by_id: 25078067: error:25078067:DSO support routines:WIN32_LOAD:could not load the shared library Any guidance appreciated. This is my first time trying to build OpenSSL myself, and I am not wholly familiar with visual studio build on top of that. Thanks! Click here<https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ==> to report this email as spam. This message has been scanned for malware by Websense. www.websense.com
