> > "Associated Data" is something if you want available in the clear not > encrypted. One example would be fields of the IP packet header. So if you > protect your IP traffic via IPsec or such, it would make sense to use AEAD, > encrypting the packet payload, but putting the packet header (well, some of > its fields - because there are fields that must change with each Internet > hop) in "adata". Reason - that IP packet will probably go through many > routers on its way from its source to destination, and unless it's header > data is in the clear, those routers won't be able to pass the packet to its > destination. > Thank you! Now I see that in my case AEAD is not needed.
BouncyCastle (Java) and Oracle Java throw an exception. I don't remember > whether Crypto++ returns an error or throws an exception - you can > experiment and report here (or look at the source :). > OK, I'll try to implement this, and then I'll write back. -- -- 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.
