On Tuesday, July 2, 2019 at 11:04:10 AM UTC-4, Mouse wrote: > > What do you know, you're right! Thank you for finding the issue, and > proposing the fix. > > Applied in the master. > > On Tue, Jul 2, 2019 at 9:54 AM Andrew Wason <[email protected]> wrote: > >> >> On Monday, July 1, 2019 at 9:58:12 PM UTC-4, Mouse wrote: >>> >>> >>> So, no - the above change does *not* look like a bug. >>> >> >> >> I don't think that change is the bug, the bug is that SymmetricEncrypt >> (and >> SymmetricDecrypt) did not also change to use MAC::DIGESTSIZE at the same >> time. It continues to use MAC::DEFAULT_KEYLENGTH >> >> Fixing that in master and it works properly with NULLHash: >> > Andrew, I think we got things sorted out. We added some ECIES known answer tests using Crypto++ 5.6.2 as the source. Uri also added a NullHash test. Then we fixed SymmetricEncrypt.
The kat's are working as expected with Crypto++ 5.6.2 and Master. Can you verify the issue has been cleared with your code? Jeff > -- You received this message because you are subscribed to "Crypto++ Users". More information about Crypto++ and this group is available at http://www.cryptopp.com and http://groups.google.com/forum/#!forum/cryptopp-users. --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/cryptopp-users/b1a27c90-385a-4e1b-8798-254e328cc42f%40googlegroups.com.
