Forget that, I was talking rubbish. The problem seems to have occurred because I was using a b**tardised version of the source consisting mostly of cryptopp560 but with an updated copy of rijndael.cpp.
When I switch the whole lot to the HEAD of the trunk the problem disappears. On Jul 30, 12:08 pm, Tom <[email protected]> wrote: > Hi all, > > When I use valgrind with my application it reports: > > ==6920== Use of uninitialised value of size 8 > ==6920== at 0x7DF95EB: > CryptoPP::Rijndael::Base::UncheckedSetKey(unsigned char const*, > unsigned, CryptoPP::NameValuePairs const&) (rijndael.cpp:280) > ==6920== by 0x7D0CEE5: > CryptoPP::SimpleKeyingInterface::SetKey(unsigned char const*, unsigned > long, CryptoPP::NameValuePairs const&) (cryptlib.cpp:56) > ==6920== by 0x7DF6312: > CryptoPP::RandomPool::GenerateIntoBufferedTransformation(CryptoPP::BufferedTransformation&, > std::string const&, unsigned long long) (randpool.cpp:38) > ==6920== by 0x7D0D984: > CryptoPP::RandomNumberGenerator::GenerateBlock(unsigned char*, > unsigned long) (cryptlib.cpp:260) > ... my code ... > > This is with r488 of "rijndael.cpp", where line 280 is: > > word32 x = (word32(Se[GETBYTE(temp, 2)]) << 24) ^ > (word32(Se[GETBYTE(temp, 1)]) << 16) ^ (word32(Se[GETBYTE(temp, 0)]) > << 8) ^ Se[GETBYTE(temp, 3)]; > > It looks like the issue is with "Se" which whilst declared in > "rijndael.h" never seems to get initialised anywhere in the code. > > Can somebody explain what/why is going on? > > Thanks, > > Tom -- 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.
