FIPS Static Library linked into Win32 Dll builds but fails self test

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Feb 02, 2016, Neptune wrote:

> FIPS Object Module 2.0.9 
> OpenSSL 1.0.1l 
> Platform: Win32 
> 
> I am attempting to statically link a FIPS-capable library into a .dll. The
> .dll is built without errors and by viewing the .dll in a hex editor I can
> see the correct HMAC is embedded within and correct, but the self test is
> failing. 
> 
> Originally I had built the FIPS-capable library as a dynamic library, but
> during testing we experienced address clashes since the libeay32.dll
> requires a fixed address and there is no way to guarantee an address we
> choose will always be vacant, so static linking is a requirement. 
> 

You'll hit the same issue if you link the static version of OpenSSL into a
DLL. The only way to escape it is to link the static version of OpenSSL into
the executable or use Win64 which doesn't have this problem.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux