On Sunday, September 11, 2016 at 1:29:01 PM UTC-4, Jeffrey Walton wrote: > > Hi Everyone, > > Crypto++ 5.6.4 was released today. > > The release notes and list of issues fixed can be found at > http://www.cryptopp.com/release564.html. The 5.6.4 ZIP archive can be > downloaded from http://www.cryptopp.com/cryptopp564.zip. > > The checksums for the 5.6.4 ZIP archive are: > > * SHA1: effa1770b81dfe05db48ddc0468ead8660929650 > * SHA256: > be430377b05c15971d5ccb6e44b4d95470f561024ed6d701fe3da3a188c84ad7 > > The 5.6.4 sources can be checked out from GitHub using the following. It > is tagged as CRYPTOPP_5_6_4 at GitHub. > > * git clone http://github.com/weidai11/cryptopp.git cryptopp > > There are 21 outstanding issues. 20 of them are feature requests. The > remaining 1 is a failed compile under GCC 4.8/4.9 in a Debug build using > -O0 and SSE intrinsics. >
The version number in Master was bumped to 5.6.5 in accordance with http://cryptopp.com/wiki/Release_versioning#Post-Release_Increment . I know it solves the disambiguation problem in theory. Let's see how well it works out in practice... 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.
