On Thursday, August 16, 2018 at 2:32:15 AM UTC-4, Andrew Marlow wrote: > > Hello everyone and especially Jeff :-) > > I wonder when the next version of cryptopp is going to be released. > > The project I am on is using 563 and we need to change to avoid some CVEs > on that release. But I am reluctant to move to either 6.0 or 7.0 because of > a couple of things: first, Jeff reported that some solaris issues have been > sorted since then and the project I am on does run on solaris as well, > where we have seen some of these issues. >
Yeah, in your case you want the non-buggy Solaris gear in Master. > Second, I would like to see something done about zlib.h so that it does > not clash with a header of the same name from the zlib library. At the > moment when any project using crypto says #include <zlib.h> the reader > cannot tell from this statement which header the coder intended. I think > that either the header should be renamed or qualified by a subdirectory > such as cryptopp so the code would read #include <cryptopp/zlib.h>. > We likely won't be changing header names. You will need to find a local workaround. We can probably release in a couple of days. We've added another 6 or 8 algorithms and fixed those Solaris bugs. Now would be a good time for a point release to 7.1. The wrinkle is, the ABI broke when adding AlgorithmProvider() so we need to bump to 8.0. For an 8.0 release I wanted more in it. But like I said, we can release with less considering we've got some [overdue] bug fixes you need. Jeff -- 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]. For more options, visit https://groups.google.com/d/optout.
