Hello,
Does anyone know how to produce a FIPS-capable OpenSSL that works on Windows NT?
I have built the latest FIPS-capable OpenSSL (openssl-fips-1.2.3) with
openssl-0.9.8r using MS Visual Studio .NET 2003 on Windows 7.
I have a small app that uses the OpenSSL library (just encrypts/decrypts). It
runs fine on Windows 7/32-bit.
But when I run it under Windows NT, I get the following run-time error:
"The procedure entry point Module32NextW could not be located in the
dynamic link library KERNEL32.dll"
So I re-built the FIPS-capable OpenSSL again specifying TARGET=VC-NT in
ms/do_fips.bat. I then configured openssl-0.9.8r as follows:
perl Configure VC-NT ...
And then rebuilt it as before. I still get the same run-time error on Wiindows
NT.
I did some research and determined that Module32NextW call is not available on
Windows NT (it is available on Windows 2000 and above).
So is it possible to produce a working FIPS-capable OpenSSL without some
hacking of the code to remove calls to Module32NextW and friends?
Any ideas?
Thanks,
Bill
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
