On Tue October 4 2011, William A. Rowe Jr. wrote: > On 10/4/2011 10:45 PM, Bill Durant wrote: > > > > Does anyone know how to produce a FIPS-capable OpenSSL that works on > > Windows NT? > > It's likely not possible... > > > 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" > > If you use the equivalent of nm against the fipscanister.lib, I'd expect > you'll find the binding there. > > I see no reason the team would accommodate this in OpenSSL/FIPS 2.0, though. > Support for Windows NT 4.xx ended on December 31, 2004. >
I can think of one reason to continue support for Windows NT 4.++ There are people in the world that run it on Alpha machines and NT 4.xx was the last Windows release to support that processor. But the O.P. did quote "KERNEL32.dll" which isn't present on the 64 bit Alpha, so that isn't their reason for using NT 4.++ Might be the same story for MIPS hardware, can't recall for sure. Mike > Support for Windows 2000 ended on July 13, 2010. > So updating "security" or cryptographic software > validation for such systems is something of an oxymoron. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org > > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
