On Mon March 23 2009, Uma G. Nayak wrote:
> Hi,
> 
> fips_test_suite executable runs just fine on these machines. All its tests 
> are successful.
> 
> How to check for SSE2 support on these machines? I have no clue about it.
>

Some OS make it easy, others make it hard(er) - - -

First, make a list of processor make/model shown by whatever system info 
utility you have;

Are they the same, different?  If different, any pattern with the machines that 
don't work?
If so, check with the published processor information, see if SSE2 is 
specifically mentioned.

Mike 
> Regards,
> Uma
> 
> -----Original Message-----
> From: owner-openssl-us...@openssl.org 
> [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. Stephen Henson
> Sent: Tuesday, March 17, 2009 8:58 PM
> To: openssl-users@openssl.org
> Subject: Re: Server crash while starting service
> 
> On Tue, Mar 17, 2009, Uma G. Nayak wrote:
> 
> > Hi All,
> >
> > We have upgraded Openssl in our application to Openssl-fips-1.2 along with 
> > Openssl-0.9.8j, so that we can run the server (Apache webserver) in FIPS 
> > mode. After the changes, the server works fine in FIPS mode, on most of the 
> > systems, except for these two machines, where the server refuses to start 
> > when launched from services.msc. The error it gives is: "Error 1053, Failed 
> > to launch the application in a timely fashion" or sometimes: "Could not 
> > start the requested service. Error code sytem-specific errorcode - 1".
> >
> > When I try to run the application in the debug environment, it gives the 
> > following error:
> >
> > FIPS_R_UNSUPPORTED_PLATFORM "unsupported platform". (Indicating that the 
> > validity of the digest test is unknown for the current platform.)
> >
> > Could this be the same error condition causing the server crash in release 
> > build. We have no way to find the cause in release build, because no log 
> > files are created by the time the server stops loading itself.
> >
> > Note: The same application works fine, if I run it in NON-FIPS mode.
> >
> > All the machines are 32 bits machines, Windows XP, RAM 1 or 2 GB. Can 
> > anyone let me know, why we are facing this problem and/or the workaround 
> > for this?
> >
> > We are grateful for any help provided.
> >
> 
> Try running the fips_test_suite executable on the failing machines.
> 
> The failing ones aren't old machines not supporting SSE2 are they? If so you
> can still run the slower version with assembly language support, see user
> guide for details of how to build it.
> 
> 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
> 
> http://www.mindtree.com/email/disclaimer.html
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> User Support Mailing List                    openssl-users@openssl.org
> Automated List Manager                           majord...@openssl.org
> 
> 


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to