If you encrypt a message on linux using AES256 and then dump to a file, and then encrypt a message on windows using AES256 and then dump to a file, the message dumps are clearly not the same. You can verify using a binary byte for byte comparison of each dump. Already a flag should go up that you cant send encrypted AES256 across platforms.
Then if you take the linux dump (which contains the message encrypted in AES256) over to windows and try to decrypt the message using AES256, you get an: InvalidCiphertext what(): StreamTransformationFilter: invalid PKCS #7 block padding found Logically this would follow. Each dump should be identical and in order for the other platform to read the message, it needs to be the same. This is not the case, so it leads to an cryptopp exception. If you take that message and read it on the same platform, the message decrypts fine. This also shows how the validation tests are able to pass and why the validation tests wont catch this type of issue. The validation tests don't test the compatibility across platforms. They would only catch issues on the same platform. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cryptopp-users?hl=en -~----------~----~----~----~------~----~------~--~---
