On Tue, Sep 28, 2010, Vivek Madani wrote: > <Clipped earlier communication> > > >> > >> What OS is this running on? That error can be caused by a DLL being loaded > >> to > >> an address that is already in use under Windows and relocation would > >> invalidate the signature. > >> > >> You can work around that by specifying an alternative load address when the > >> DLL is compiled. > >> > > > > This is Win2K3 on a virtual machine. I thought about the load address > > and is looking through ProcessExplorer to see where the conflict is. > > Will try a recompile. > > > > One more query: Shouldn't fips_test_suite.exe report failure as well? > That passes without any issues.
No, fips_test_suite and the other fips algorithm test utilities are not linked against libeay32.dll but statically linked against fipscanister.lib: as a result they wont see the conflict. 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
