> Heh, well, if you know anything about the fips build process > on windows, you know FIPS-1.1.2 (based on OpenSSL 0.9.7) will > only compile for 32bit Windows since it requires the use of > Mingw/MSYS to build the fips canister. Since Mingw/MSYS is > only available as a 32bit compiler (well, there are 64bit > snapshots now, but most likely the build scripts aren't aware > of that since FIPS 1.1 predates any 64bit mingw), you're not going > to get a 64bit windows binary with the currently validated FIPS > release.
Depending on how much OpenSSL functionality you need, it shouldn't be too terribly hard to wrap a 32-bit library for use on a 64-bit platform by other 64-bit modules. I have had to do the reverse in the past where I could only get OpenSSL to build as a 64-bit library on some platform (Digital UNIX?) and my application was not ready to compile on a 64-bit platform. It's made harder by the fact that many OpenSSL 'functions' are really macros that pull guts out of OpenSSL structures. But if you can make a COM object or other kind of 'server' out of the OpenSSL library, you should be able to use a 32-bit Win32 binary on a 64-bit Win32 platform along with other 64-bit executables. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
