Steve:

Thanks for your response.!

1) Will there be an issue if we change the names from ssleay32.lib -> ssl.lib and libeayfips32.lib -> crypto.lib . I remember reading on some forms that changing the names of the library which are generated by* fips build does cause issue. Is this true..?

2) Also while building fips, does it support buiding binaries with debug, non-debug, single thread and mutitreaded like how openssl does..? or will there be any issues. I could not find this in the user guide docs. If there is another reference please point to that.

Thanks,
JA


--- On Thu, 10/16/08, Dr. Stephen Henson wrote:
From: Dr. Stephen Henson
Subject: Re: fips 1.2 build on windows VC 9
To: openssl-users@openssl.org
Date: Thursday, October 16, 2008, 1:38 PM

On Thu, Oct 16, 2008, Justin A wrote:

>
> My Question is:-
>
> 1) I remember when I previously build openssl I used to end up getting
> libcrypto.lib and libssl.a. Now its ssleay32.lib and libeayfips32.lib
> instead of libssl.a and libcrypto.a respectively. I ran the dumpbin on

these
> two libraries and it does have all the ssl and crypto symbols. nt.mak file
> also have these names defined. So is this the right naming convention..?
>


Yes in 1.1.2 we had to use a Unix like build environment under Windows in
order to have the same build procedure on all platforms.

This is no longer the case and VC++ can be used throughout.

Note that you can also use a recent 0.9.8 snapshot as the FIPS changes have
now been merged into 0.9.8.

> 2) Are the steps which I followed to build the FIPS capable openssl steps
> right..?
>


Well it is a test version and not validated at present, but yes they are
correct.

Steve.
--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSSL project core developer and freelance consultant.
Homepage: http://www.drh-consultancy.demon.co.uk
__________________________________________________ ____________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majordomo@openssl.org