I also noticed that the fips140 code requires that fipstest.cpp be
included in the build. This then pulls in most everything else.
I was trying to do a minimal build of the code required for the
RSA module. The RSA code calls two of the test routines in fipstest.
I just added the following to fips140.cpp to allow the minimal
library to build without all the routines that fipstest needs.
#if !CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2
void EncryptionPairwiseConsistencyTest(const PK_Encryptor &encryptor, const
PK_Decryptor &decryptor)
{
}
void SignaturePairwiseConsistencyTest(const PK_Signer &signer, const
PK_Verifier &verifier)
{
}
#endif
It would be nice if this (or similar) change could be included in a 5.x
release.
Thanks for the great work.
-----Original Message-----
From: Wei Dai [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 20, 2002 4:01 PM
To: Crypto++ Mailing List
Subject: FIPS 140 build configuration
Several people have been confused about the FIPS 140 build configuration in
the MSVC project files. It should only be used by myself to build static
libraries that then need to go through the FIPS evaluation process.
Right now it's the default configuration when you first load up
cryptest.dsw. According to a Usenet post, MSVC sets the last configuration
in a .dsp file as the default. I'll try editing the .dsp file manually and
see if I can set the default to something else.
