We just noticed that building the fips module on Linux works fine with
no-asm, but on a 64-bit Windows build, it doesn't work without no-asm.
Here's the error:
link /nologo /subsystem:console /opt:ref /debug
/out:out32dll\fips_standalone_sha1.exe
@C:\Users\TyrelHa\AppData\Local\Temp\nmAD0D.tmp
sha1dgst.obj : error LNK2019: unresolved external symbol
fips_sha1_block_data_order referenced in function fips_sha1_update
sha1-x86_64.obj : error LNK2019: unresolved external symbol
OPENSSL_ia32cap_P referenced in function sha1_block_data_order
out32dll\fips_standalone_sha1.exe : fatal error LNK1120: 2 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 10.0
\VC\BIN\x86_amd64\link.EXE"' : return code '0x460'
Stop.
I don't know enough about the openssl build yet to be able to resolve
this one myself. It works fine if no-asm is specified to Configure.
Can someone take a look?
Thanks!
Tyrel
On Wed, Jun 29, 2011 at 2:14 PM, Steve Marquess
<marqu...@opensslfoundation.com> wrote:
> On 06/29/2011 04:46 PM, Dr. Stephen Henson wrote:
>> On Wed, Jun 29, 2011, Tyrel Haveman wrote:
>>
>>> Thanks Steve. This helps a lot. One more related question: Why are the
>>> FIPS test vectors different for different platforms? It seems like
>>> Windows and Linux, for example, should both be able to encrypt the
>>> same things and produce the same outputs.
>>>
>> They are interchangable it's just that those are the testvectors produced by
>> that particular platform during testing.
>
> The formal testing process requires that a unique set of test vectors
> (request files) be generated for each test platform ("operational
> environment"). Once such a set is used for one platform and the
> response files confirmed as correct it cannot be used again for any
> formal testing. Presumably that is to keep the vendors (i.e. us) from
> cheating by hard-coding the correct answers. By now we have encountered
> quite a few of these test vector sets, but as they are interchangeable
> there is no point in keeping more than a few representative samples.
>
> -Steve M.
>
> --
> Steve Marquess
> OpenSSL Software Foundation, Inc.
> 1829 Mount Ephraim Road
> Adamstown, MD 21710
> USA
> +1 877-673-6775
> marqu...@opensslfoundation.com
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> Development Mailing List openssl-dev@openssl.org
> Automated List Manager majord...@openssl.org
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
