Hi Everyone,
We have a new release candidate available at
https://www.cryptopp.com/cryptopp563rc5.zip. Here are the checksums:
$ md5sum cryptopp563rc5.zip
fc262c405b350f11f36aafa50f4d4752
$ sha1sum cryptopp563rc5.zip
3e6ab5e68f88a809d332d14b0dd301a0389cc2ee
$ sha256sum cryptopp563rc5.zip
3c345cff42d7d6db1c3eb980132b07e283a6616d450995bb03195499db183f39
We still need to cut-in the RDSEED stuff, but it should be painless based on RDRAND.
This RC also addresses VCUpgrade problems at VS2010 caused by the
MSBuild changes (or maybe, more correctly, the deficiencies in
VCUpgrade).
-----
The VCUpgrade problems were addressed by providing a vs2010.zip as part of the
distribution. Just unpack the ZIP over top the existing files, and the
solution and project files will become VS 2010. You can also delete the
*dsw *.dsp *.vcproj files.
We were able to clear nearly all the
VCUpgrade issues, and 20 of 24 configurations build from the IDE. The
remaining 4 must be built from the command line because we can't seem to
express the dependency needed to make the machinery work as expected.
The configurations that don't build are the DLL-Import pieces of the
Cryptest project. In normal use, the Cryptest/DLL-Import configurations
are not usually built, so its not a hardship. The FIPS DLLs build OK; the problem is getting the DLL-Import Cryptest to use the export library.
If
you try to perform an VCUpgrade yourself, then the first thing you have
to do is delete the Assembly References VS2010 puts in place of
dependencies. Then, you should reconstruct the dependencies by hand. The
VS2005 projects were modified so linker paths and libraries are present
after the VCUpgrade, which should save 8 to 12 failures from
Microsoft's decoupling of the projects under MSBuild.