Hi Wei, The latest changes were very welcomed. Thanks. Three loose ends on CCM and GCM modes
AuthenticatedEncryptionFilter takes a std::string mac channel parameter. I was able to get Crypto++ to toss many exceptions during testing; but I could never coax a separate channel for the tag. I believe I tried to send the mac in on the channel, and get the mac out on the channel. Is it needed? Defineing MAC_AT_END (=0) to compliment MAC_AT_BEGIN for AuthenticatedDecryptionFilter flags may help others and aid in source code readability. I understand the default channel can be specified as NULL_CHANNEL. But using NULL_CHANNEL makes me feel like data is being discarded by sending it to the bit bucket. 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. -~----------~----~----~----~------~----~------~--~---
