This has been suffering feature creep in a bad way... I'm going to step back and approach it as a maintenance release: take the 5.6.2 release, add the CVE fix, add the minor errata fixes, and then offer it as 5.6.3.
We'll tackle the additional features in 5.7, which is right behind 5.6.3. Jeff On Friday, July 24, 2015 at 3:39:12 PM UTC-4, Jeffrey Walton wrote: > > Hi Everyone, > > A few folks have asked about a Crypto++ 5.6.3. I think we are at (or near) > the release. > > As of today, we are -Wall -Wextra clean; and UBsan and Asan clean. We have > no detected issues under Valgrind. We cleared a few minor errata items and > Sidorov's CVE. > > I think that's a really good baseline, and clearing the minor errata items > warrants a minor/revision bump. > > I don't think we should include HKDF and Base64URLEncoder in a revision > release, so I was going to subtract them manually. They can be included in > 5.7 or 6.0. > > Is anyone opposed to 5.6.3? If so, now is the time for comments or > objections. > > ***** > > -- -- 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. --- 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]. For more options, visit https://groups.google.com/d/optout.
