On Tuesday, January 17, 2017 at 5:39:28 PM UTC-5, Joachim Achtzehnter wrote: > > In older versions of Crypto++, for example v5.2.3, the ProcessData() > function of CFB_FIPS_Mode<AES>::Decryption worked with arbitrary sizes of > input packets. In recent versions, at last since v5.5.2, it causes an > assertion if the input packet is not a multiple of the block size. CFB > should not require this constraint. Is this a known bug? >
Wow, that's going back in time. Rijndael::ProcessData requires a full block size. I'm not sure what CFB_FIPS_Mode::ProcessData is doing at the moment. The mode can clearly process bytes at a time, but it should ensure a full block is being sent to Rijndael for processing. Do you have some sample code so I can inspect things under your setup? Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com. 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
