Hi Jeffrey, > Perhaps, but there should not be. The Crypto++ library is NIST > certified. This means (among other things) NIST tested the Crypto++ > implementations (the binary was provide by Wei to NIST). If there is a > difference, I would expect it to lie outside of Crypto++.
I have been busy last days. I did a quick test with the XySSL AES implementation. It was very interesting. The implementation seems to act like Crypto++. The results were equal. Still dont know, why the PHP and Python script produces other hex values - except the first byte. > The best I can recommend to verify the integrity of Crypto++ on you > (Linux?) installation is to run the validation test. I believe it is > ./cryptest.exe -v. If you tank on validation, all bets are off. > Perhaps the WINE emulator is causing you grief. I checked the Crypto++ installation on my windows machine. The validation test passed successfully. > FIPS 197, Appendix C includes AES test vectors > (http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf). Have > you had an opportunity to run them through mcrypt? > > Finally, FIPS 800-38A > (http://csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf) > specifies five modes of operation (CFB is one of them). Test vectors > are included in Appendix F. CFB mode is Appendix F, Section 3. Thanks for the resources! I will check it out. Best regards, Stephen --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
