RE: Crypto++ 5 problems on VC 6.0 ?

Frederic Vicher Thu, 8 May 2003 06:55:57 -0400 (EDT)

Hi Jeff,

thanks for the tip. I created an empty edc.dat file and now the program gives the usage. But there is no message concerning a hash value. When I start cryptest with a command (I tried a few ones), I always get the message:

CryptoPP::Exception caught: Cryptographic algorithms are disabled after power-up a self test failed.

I even tried the fips test. It was worse:

0. Caught expected exception. Exception message follows: Cryptographic algorithms are disabled before the power-up self tests are performed. 1. Caught expected exception when simulating self test failure. Exception message follows: Cryptographic algorithms are disabled after power-up a self test failed. Power-up self test failed.

abnormal program termination

The build is a non-FIPS one (Win32 Debug), and this is confirmed by the fact that the cryptest.exe file is generated in the CTDebug directory and not the CT_FIPS_140_Debug one (I don't have any CT_FIPS_140 or CT_FIPS_140_Debug directory). Thus I wonder if there is not a problem with a conditional build statement somewhere in a file.

Is anybody here able to check this?

Thanks,
        Frederic

At 14:07 07/05/2003 -0400, you wrote:

| -----Original Message-----
| From: Frederic Vicher [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, May 07, 2003 1:42 PM
| To: [EMAIL PROTECTED]
| Cc: '[EMAIL PROTECTED]'
| Subject: RE: Crypto++ 5 problems on VC 6.0 ?
|
| ...
|
| Thus I started the test and got the message:
|
| I got the same message
| as with the 5.0 version:
|
| CryptoPP::Exception caught: FileStore: error opening file for
| reading:
| H:\usrprog\crypto51\edc.dat
|
| Thus the remaining question:
| What's the edc.dat file and how to get it? I confirm that I'm
| not using a
| FIPS 140 configuration (thanks again for the link).
|
| Thanks,
|          Frederic
|

Hi Frederic,

The edc.dat file is a hash of the program (IIRC). Wei uses it for testing
(and other's use it as required). I'm not sure how along the FIPS 140
compliance is. I was thumbing through the document (see
http://csrc.nist.gov/cryptval/140-2.htm), and its quite a handful.

1) Actually generate the hash of the exe.
OR
2) Create an empty edc.dat file. When you run the FIPS build, you will get
an error that the hash should be some value. Copy that value into the file,
and you should be on your way.

If you would like to work with a non-FIPS build in VC:
From the Build Menu, Select 'Set Active Configuration...'
In the Dialog, chose 'cryptest - Win32 Debug'

Jeff

RE: Crypto++ 5 problems on VC 6.0 ?

Reply via email to