Fixed this and found one of the most common problems in my code: that's not a good idea to provide ANY functions, working with "char" or "byte" data, with a link to SecByteBlock, as in this case such functions would overwrite not the byte buffer, but all the SecByteBlock. Fro example, standart fstream::read() function does this, and this code: In.read((char *)&sblock, sblock.size()) leads to bad results! Why is there no way to get a byte pointer from SecBlock? It can only return const byte pointer! P.S. Still debugging, hope to finish that in a couple of days.
-- -- 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 Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
