I understand what you're saying for #2 now, the hexEncoding of the IV works fine, it's just the decoding that causing the problems when it hits 0x00.
So, I need to know how to use my current hexDecode function to instead of outputting to a std::String, to be a CryptoPP::SecByteBlock, how can I adjust my current code to fit this? I've never used a PBKDF before, nor can find anything in the validat# files to help me, is there any sample code out there that can help me do so, keeping in mind that AES-256 requires the 32 bit key length. -- View this message in context: http://old.nabble.com/AES-Problem-tp31186698p31216023.html Sent from the Crypto++ Users mailing list archive at Nabble.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.
