I've recently been working with the FIPS compliant release, and I've found that the DllTest executable will usually not successfully complete in Release mode:
Compiler: Visual C++ 6.0 SP5
Program Output:
=-=-=-=-=-=-=-=
0. Automatic power-up self test passed.
1. Caught expected exception when simulating self test failure. Exception messag
e follows: Cryptographic algorithms are disabled after a power-up self test fail
ed.
2. Re-do power-up self test passed.
3. DES-EDE3-CBC Encryption/decryption succeeded.
4. SHA-1 hash succeeded.
[crashes here]
Call Stack:
=-=-=-=-=-=
NTDLL! 77f7f570()
NTDLL! 77fac6ec()
NTDLL! 77f8cf62()
NTDLL! 77f5e449()
MSVCRT! 77c2ab2e()
DLLTEST! operator delete(void *) + 9 bytes
DLLTEST! CryptoPP::DL_PrivateKey<class CryptoPP::Integer>::MakePublicKey(class CryptoPP::DL_PublicKey<class CryptoPP::Integer> &) + 145 bytes
DLLTEST! CryptoPP::AssignFromHelperClass<class CryptoPP::DL_PublicKeyImpl<class CryptoPP::DL_GroupParameters_DSA>,class CryptoPP::DL_PublicKey<class CryptoPP::Integer> >::AssignFromHelperClass<class CryptoPP::DL_PublicKeyImpl<class CryptoPP::DL_GroupParameters_DSA>,class CryptoPP::DL_PublicKey<class CryptoPP::Integer> >(class CryptoPP::DL_PublicKeyImpl<class CryptoPP::DL_GroupPar +
DLLTEST! FIPS140_SampleApplication(void) + 1678 bytes
DLLTEST! main + 5 bytes
DLLTEST! mainCRTStartup + 227 bytes
KERNEL32! 77e7eb69()
Checking the project Source\cryptodll.dsp, I noticed that the release executable is set to use the "Multithreaded" run-time library, and not "Multithreaded DLL" as the DllTest project is set to. However, I discovered that either build would run correctly with the Source\DLL_Release version of DllTest, and rebuilding the root DllTest with the Source\DLL_Release lib and dll would allow that one to run correctly as well.
Looking at the "Crypto Officer Guide and User Guide", it instructs how to build a Debug version of DllTest to validate the application. I was wondering if the Release version was possibly left untested?
The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, forwarding, or otherwise copying of this message is strictly prohibited. If you have received this communication in error, please notify Padcom immediately by e-mail at [EMAIL PROTECTED] and delete the original message. Although Padcom utilizes industry accepted methods to scan email and attachments for viruses, it does not guarantee that either is virus-free and accepts no liability for any damage sustained as a result of viruses. Padcom makes no representation or warranty (express or implied) as to the accuracy or completeness of any information provided in this e-mail message and expressly disclaims any and all liability that may be based on information contained therein.
