We can't release 5.6.3 yet. Am 24.07.2015 um 21:39 schrieb Jeffrey Walton: > 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. I think dropping HKDF from here is ok, because we /know/ that the interface will change soon. Concerning the Encoder I'm not too sure. Generally adding stuff seems to be considered ok for minor releases (5.6.2 got Keccak) so the encoder may stay.
> > Is anyone opposed to 5.6.3? If so, now is the time for comments or > objections. > > ***** > > If there are no comments or objections, I will start a "deep testing" > release cycle. During the deep dive, I will build the ZIP, and test > the following workflow on my test machines and GNU's test farm: > > unzip -a cryptopp-5.6.3.zip > cd cryptopp-5.6.3 > make > make clean > make > make distclean > make > make check > ./cryptest.exe v > ./cryptest.exe tv all > > If all goes well, I will perform the version bump so that references > to versions 5.6.2 are changed to 5.6.3 (like README.txt). I will then > perform the "Preparing for 5.6.3..." check-in. > > After the check-in, I'll get with Wei and we can place the new ZIP on > the website. > > ***** > > Since the project is VS 2008, I will stand up a test machine with that > particular version of VS. > > Open question: what versions of Visual Studio should be supported? It would be nice if VS 2005 would be supported but I guess we don't have to (let it stay untested?). I think VS 2008 should be supported. I also think that VS 2010, VS 2012, VS 2013 and VS 2015 need to be supported (-> no warnings during compilation at standard W3, 5.6.2 did this on all supported versions (up to 2012)). > > Are we fixed at 2008? Or should we also test a conversion to something > contemporary, like VS2012 or VS2015? We should test it (2008, 2010, 2012, 2013, 2015). At the moment I'm testing the build (and the potential fixes) with VS 2015 (community edition), I'll write a mail about progress later this day. BR JPM > > ***** > > Jeff > -- > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- -- 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.
smime.p7s
Description: S/MIME Cryptographic Signature
