That doesn't sound good. Luckily we have a test-tool for this purpose.
Can you please run (on both machines, from the Crypto++ main directory) cryptest.exe v and cryptest.exe tv all and append the results? This will run standard validation tests and test vector tests and will report whether there is something not OK with the library. BR JPM Am 01.06.2016 um 20:14 schrieb [email protected]: > I send AES256 on ARM (linux, bsd) to x86-64 (linux) and decrypt. I'm > crossing an endian boundary and OSs. I can only conclude it is your > code, or a compiler flag. Probably on the windows side, as that is the > only platform I don't touch. > > -- > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- -- 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.
