After checking the docs for Crypto++ I regret to report that this library (currently) does NOT support Rijndael, but only AES - using two names for the same algorithm (AES).
Disappointing... -- Regards, Mouse On Dec 23, 2012 5:33 PM, "Jeffrey Walton" <[email protected]> wrote: > On Dec 23, 4:02 pm, Jamaal Scarlett <[email protected]> wrote: > > I was able to plug the memory leak in mcrypt, but I appreciate the > > assistance. I will definately be using Crypto++ for my next encryption > > project. > If you are [will be?] interop'ing with scripting languages, take a > moment to read: http://www.cryptopp.com/wiki/HexEncoder. > > It has a topic on converting parameters (such as keys and > initialization vectors) to binary. > > Jeff > > -- > 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.
