On Wed, Mar 09, 2011, Collins, Jerry wrote: > Stephan, > Maybe I'm confused, and it's been two years since I dealt with this, > but I thought the libeayfips32.lib was built as part of the fips build, > not as a follow on step. Also, the libeay32.lib that is built by the > ms\do_fips no-asm doesn't give me an option of whether to build a DLL or > static library. It automatically builds a DLL. >
The build process has changed since the 1.1 module: which had to use MingW. The 1.2 modules uses VC++ throughout and you need two steps. The reason you build a FIPS capable OpenSSL is so you can keep up to date with security and bugfixes outside the validated code. 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
