On Sunday, September 13, 2015 at 10:05:48 AM UTC-4, jean-pierre.muench wrote: > > Am 13.09.2015 um 11:58 schrieb Jeffrey Walton: > > Hi Everyone, > > We have a new release candidate available at > <https://www.cryptopp.com/cryptopp563rc1.zip>https://www.cryptopp.com/cryptopp563rc2.zip. > > Here are the checksums: > > The link is broken and points to cryptopp563rc1.zip. >
It seems to be working for me from both Firefox and cURL command line. Maybe there's a problem with the browser you are using? $ curl -cacert CAcert.pem https://www.cryptopp.com/cryptopp563rc2.zip -o cryptopp563rc2.zip % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1150k 100 1150k 0 0 624k 0 0:00:01 0:00:01 --:--:-- 642k > $ md5sum cryptopp563rc2.zip > 8be71145deecfde7e64a1e05c3d5e82b > $ sha1sum cryptopp563rc2.zip > c3431e2c2778e6dcb0e12ba4530f720b31efdb1d > $ sha256sum cryptopp563rc2.zip > 876822292ffc56ced28bf1ef3811aa8299919fcea22df76dbed51924267c6e18 > > We needed to update the source code due to an ARMEL workaround under GCC > 5.2 at/above -O2 for the integer class. See > https://github.com/weidai11/cryptopp/issues/31. > > Since the change was non-trivial, it kicked-off another round of testing. > Because one non-trivial change was added, another was added to algparam.h. > The change removed the last significant portion of latent undefined > behavior by limiting the VC 6.0 hack to VC 6.0 only (after verifying it did > not change the symbols or layout of objects). See > https://github.com/weidai11/cryptopp/issues/5. > > As with the other RC's, there's a diff completely showing the differences > between the RC and Crypto++ 5.6.2. > > I've downloaded and tested RC2 on VS 2015 (Win7 HP x64) and it's working. > > However I'm facing a minor issue that it looks like VS2015's project > converter drops custom build instructions which means (for me) that the > .asm files won't be assembled and thereby causing linker errors in the > other projects. > Yeah, the MSBuild changes from 2010 are [still] causing a fair amount of trouble. I think we are going to have to act. I'd prefer to leave it for Microsoft or users to sort out since its an IDE issue. After 5 years, its obvious Microsoft is not going to fix it. And some users depend on the accessibility features, and I think fixing it is the responsible thing to do for them. 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]. For more options, visit https://groups.google.com/d/optout.
