Thanks. And..your sound like 'CFB implementation is not specified'. is that right? Or, Crpyto++ just improve about this? Could you tell me about this?
On 6월28일, 오후8시46분, "Geoff Beier" <[EMAIL PROTECTED]> wrote: > > PHP-mcrypt on Centos 5.1 based and crypto++ library make little > > different output like this. > > Is it not a bug or not? > > > PHP : :0x3D(61).0x15(21).0x69(105).0xCD(205).0x57(87).0xD5(213). > > 0x00(0).0x00(0).0x00(0). > > Crypto 5.5.2: 3d 19 a1 60 b3 7d 00 00 00 00 00 00 0 > > > Which side was wrong? Who can handle this? > > I suggest you talk to the developers of PHP-mcrypt. They default to > 1-bit CFB mode. Crypto++ defaults to 128-bit CFB mode. 128-bit CFB is > a much better idea :-) > > See this thread for additional > details:http://groups.google.com/group/cryptopp-users/browse_thread/thread/c9... > > HTH, > > Geoff --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
