Hi Wei Dai, hi folks I could figure out why the MAC generation step sometimes fail. It's a naming problem. The custom build step uses the fixed name cryptdll while the the output of the project shall be cryptopp. So I think all that have to be done to fix this problem is adapt the names and proberbly set the name in the custom build rule to a dynamic variable or at least to the right name.
As you see my first problem is fixed. Unfortunately I directly run into the next one. Also during the power-up self test. Now the AES test (Rijndael causes an error rijndael.cpp line 945 "space = (byte *)alloca(255+sizeof(Locals));" causes at any point an access violation error. Is there a known problem? Frank 2010/8/2 Wei Dai <[email protected]> > On Visual Studio 2010, sometimes the MAC generation step fails, and I'm > not sure why. Try running the custom build step again. Or you can just > modify the source code and disable the MAC checking step, since it's only > required for FIPS compliance and I don't think it adds much real security. > > *From:* Frank Fischer <[email protected]> > *Sent:* Monday, August 02, 2010 1:16 AM > *To:* [email protected] > *Subject:* Power-up self test failed > > Hi folks, > > now I'm searching for a solution for my problem for days but I can't find > anything. > > I managed to compile cryptopp 5.6 with Visual Studio 2010 with the help of > the solution provided in this group. I try to dynamically link the library > from my project. But everytime the library loads I get the message that the > power-up self test failed. I believe that depends on an error I got when > compiling the cryptopp 5.6. (cryptest.exe "Invalid allocation size: > 4294967295 bytes.") It seems that the hash to test the library is not > generated. When I step through the code while execution the expected hash is > something like MAC_<some numbers> but the generated hash is something > cryptical. I do not want to link cryptopp statically because all other > libraries I use are linked dynamically and it causes problems to mix up the > linking methods. > > Does anybody experience the same problems and have a solution or an idea? > > Frank > > -- > You received this message because you are subscribed to the "Crypto++ > Users" Google Group. > To unsubscribe, send an email to > [email protected]. > More information about Crypto++ and this group is available at > http://www.cryptopp.com. > > -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
