On Wed, Mar 25, 2009, Uma G. Nayak wrote: > Hi, > > Ok. I ran the fips_test_suite.exe and checked for the system information. I > have 2 situations. > > 1. One of the system does not support FIPS mode operation. It's an AMD Athlon > XP which does not support SSE2. Hence I built Openssl dlls using no-sse2 > flag. Even after using these new dlls I am not able to start my server. > > I want to know whether the steps I followed for building Openssl are proper. > Details: I am using Openssl-fips-1.2 and Openssl-0.9.8j modules. > > Step I for building Openssl-fips-1.2: > > perl Configure VC-WIN32 no-sse2 > vcvars32.bat > ms\do_fips > > Step II for building Openssl-0.9.8j: > > perl Configure VC-WIN32 no-asm fips --with-fipslibdir= <path_of dlls got from > previous step> > ms\do_ms > vcvars32.bat > nmake -f ms\ntdll.mak > > Is this the right way to build? If yes, what could be wrong that the server > is still not starting? > > 2. On the second machine, which is a Pentium 4 D, fips_test_suite showed all > successful tests. System configuration information did not give any hint on > SSE2 support. But Pentium 4 D supports SSE2 and above. Still why server is > not able to start? > > Can you guys out there see anything? Please tell me. >
You can't use no-sse2 as an option for building the validated tarball: that violates the security policy. You have to use no-asm instead. 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 majord...@openssl.org
