SEAL is too fast - it caused an integer overflow in the number of bytes processed. Try running "cryptest b 1" to reduce the number of seconds spent on each benchmark, or get the current code in CVS, where I've made a change to count more bytes.
On Tue, Oct 28, 2003 at 11:03:44AM -0500, Sean E. Covel wrote: > I just downloaded the Crypt++ 5.1 source and compiled it with VC++ 6, > SP6 (with the processor pack). I'm running Windows 2000, SP2. It > compiled with no errors. I then ran the validation tests (cryptest v) > and all tests passed. I then ran the Benchmarks (cryptest b 15 > > bench.html). I got no results for Adler-32, SEAL 3.0 (BE and LE), and > the Panama Cipher (BE and LE). I am particularly interested in the SEAL > algorithm. What did I do wrong? > > Here is a sample of the output: > > Algorithm Bytes Processed Time Taken > Megabytes(2^20 bytes)/Second > SEAL-3.0-BE 0 10.004 0.000 > SEAL-3.0-LE 0 10.004 0.000 > > Thanks, > > Sean
