I am a bit confused. The process is using fipslink.pl to perform the linking. I thought that was the correct process to cross compile on x86 Windows XP system for a Windows CE ARM system. BTW, I am just using the provided process to build the FIPS capable OpenSSl using the "perl Configure VC-WIN32 fips --with-fipslibdir=c:\fips\path".
I am new to OpenSSl and FIPS. Could you provide any suggestions as to what settings to change so that calculating and embedding the signature will work correctly.
Formally speaking one should wait for updated user manual, as current one says CE is not option. Obviously it should discuss CE limitations and provide more detailed instructions. Though I can't say when it will be ready, it's not on my table.
Has this been done successfully for Windows CE?
Yes, but not with dll. Even though do_fips.bat from FIPS module source refers to cedll.mak, validation is performed with statically linked applications. Probably one shouldn't have referred to cedll.mak to avoid confusion. I don't know all the details, but I'd guess it was chosen in order to keep modifications to *absolute* minimum. But it's of lesser relevance, because once you've got fipscanister.lib, you can use it in context of your liking. Of course provided that your liking is within limitations imposed by fingerprinting. Which in CE context [unfortunately] are "forget about dll [or maybe go for rom-based]."
______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
