On 09/13/2013 04:08 AM, Carl Young wrote:
Forgive me if I am wrong, but I didn't think the FIPS 2.0 code base
> could be used with anything else but MS VC on Windows!?
The user guide does not state this explicitly as far as I can see,
but the instructions - for building the canister and linking against
it - only mention MSVC based commands, which would lead me to believe
that MinGW/MSYS are not approved/tested (only for canister I mean).
Seesection 4.3, and section 4.3.1 specifically.
Carl, thanks for your comments.
You are correct when you say that the FIPS user's guide does not
explicitly mention MinGW as a target for the Windows build.
I reasoned that OpenSSL 1.0.1e itself has support for a MinGW build, so
adding in the "fips" option wouldn't be much of a stretch. Besides, my
project already uses MinGW and I need a FIPS capable OpenSSL. :-)
I did find that after the OpenSSL build fails with the "multiple
definition" errors, I could edit ms/uplink.c and crypto/uplink-x86.s and
change the conflicting symbols (ie. OPENSSL_Uplink and
OPENSSL_UplinkTable) such that they don't conflict. I used
OPENSSL_Uplink2 and OPENSSL_UplinkTable2. This allows the build to
complete.
A subsequent "make test" ends with "ALL TESTS SUCCESSFUL" and my
application is able to call FIPS_mode_set(1) successfully. So it
appears to be working.
--
Thomas J. Pinkl
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
