There's probably a bug in your compiler's code generation. If you have any compiler optimizations turned on, trying turning them off. If that doesn't work, debug it by tracing the test execution on your Solaris machine and on a platform where the code does work and compare the two to find out where they start to differ.
On Thu, May 08, 2003 at 10:44:13AM +0300, Murat Eren wrote: > Hi, > I realized that I did not run the test suite. When I run the validation tests I fail > on the following stages (previous tests pass) and receive an exception. > Running 'cryptest.exe g' results in infinite waiting. (I tried with key lengths 1024 > and 128). > Any suggestions? > > Murat :-) > > ------------------------ output of 'cryptest.exe v ' command --------------- > Using seed: 1052378644 > > > Testing Settings... > > passed: Your machine is big endian. > passed: sizeof(byte) == 1 > passed: sizeof(word16) == 2 > passed: sizeof(word32) == 4 > passed: sizeof(word64) == 8 > passed: sizeof(word) == 4, sizeof(dword) == 8 > passed: HIGH_WORD() and LOW_WORD() macros > > No operating system provided blocking random number generator, skipping test. > > No operating system provided nonblocking random number generator, skipping test. > > CRC-32 validation suite running... > > passed 00000000 "" > passed 43beb7e8 "a" > > ...... > all tests in between pass > ....... > > BlumBlumShub validation suite running... > > passed 49ea2cfdb01064a0bbb92af101dac18a94f7b7ce > FAILED 94991ada67c0ff40e02e > FAILED 48946ce9a76d2fa282b7f2b985d0560bd608f865 > > DH validation suite running... > > FAILED simple key agreement domain parameters invalid > > MQV validation suite running... > > FAILED authenticated key agreement domain parameters invalid > > RSA validation suite running... > > > CryptoPP::Exception caught: InvertibleRSAFunction: computational error during pr > ivate key operation > > > *********** REPLY SEPARATOR *********** > > On 05.05.2003 at 14:55 Wei Dai wrote: > > I just noticed this email sitting in my inbox. Have you been able to > resolve this problem? If not unfortunately I don't have access to a > Solaris machine with gcc 3.2.1 installed. I suggest that you run your test > program under a debugger on both Solaris and Windows, and trace the > executions step by step until they start to differ, and try to pin down > where the problem lies. > > On Tue, Apr 29, 2003 at 04:49:46PM +0300, Murat Eren wrote: > > Hi, > > I am using crypto51 for dsa, signing and verifying. I encountered with > the problem that same keys are validated in Windows, but not in Solaris. > Attached you will find the test program source code and keys and Makefile > for Solaris. > > I am using VC60 in windows, and g++ in Solaris. > > > > (Configured with: ../configure --disable-nls --with-as=/usr/ccs/bin/as > --with-ld=/usr/ccs/bin/ld > > Thread model: posix > > gcc version 3.2.1) > > > > Any idea? Looking forward for a solution. > > > > Murat :-) >
