On Tuesday, August 1, 2017 at 4:32:49 AM UTC-4, Jeffrey Walton wrote: > > > > On Wednesday, September 21, 2016 at 8:13:16 AM UTC-4, edwin schriek wrote: >> >> Apparently the random pool is the cause of our problems. In 5.6.4 it uses >> time and AES instead of no time and MDC<SHA> in cryptopp 4.2. >> Is there anyway to replicate the old randpool behaviour, or are there >> other possible solutions? >> > > Sorry to dig up an old thread. This topic came up again. > > I hacked together a wiki page on the subject. its available at > https://www.cryptopp.com/wiki/Old_RandomPool. > > Please let me know if it needs errors or omissions addressed. >
Now open in the bug tracker: "Add OldRandomPool for pre-Crypto++ 5.5 compatibility", https://github.com/weidai11/cryptopp/issues/452. 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.
