Hi Jeffrey,

> Can you give https://github.com/weidai11/cryptopp/commit/e06e3bd7a998 
> <https://github.com/weidai11/cryptopp/commit/e06e3bd7a998> a try?


This temporary fix makes it ok again :-)
Congratulations for getting this quickly, I am glad I could help.

> I'm not sure why our self tests did not detect the failure. I think that is a 
> bigger problem.

I can share with you the fuzzer generated corpus.
This way, you can find out different cases (even if there are ones not 
especially related to cryptopp)

Best regards,
Philippe

PS : I forgot to mention that this bug was found by oss-fuzz

-- 
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/1BA21383-E3A1-4E56-9C59-607245ED7A71%40catenacyber.fr.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to