Crypto++ 5.6.3 released

[nolo...@gmail.com]

Hi Everyone,

Crypto++ 5.6.3 was released tonight. It can be downloaded from http://www.cryptopp.com/cryptopp563.zip.

The checksums are:

  * SHA-1: bd9fbe86ec1f3dd18ed395fae307da70dc86786f
  * SHA-256: bd72e1622e84d46664ca5fb331773e8c909d7861b8cdbdb269b27759cd2a8e89

The release can be checked out from Sourceforge at:

  * svn checkout https://svn.code.sf.net/p/cryptopp/code/trunk/c5 cryptopp-svn

And GitHub (preferred, as Sourceforge is going away next):

  * git clone https://github.com/weidai11/cryptopp.git cryptopp-git

It is tagged as CRYPTOPP_5_6_3 at both Sourceforge and GitHub.

There are two outstanding issues The first is Issue 61, which is a hang under ARM64 for a Debian 8/amd64 Chroot. The second is Issue 37, which is a crash under ARM for iOS 5.1. Also see https://github.com/weidai11/cryptopp/issues.

All success should be directed to Wei, folks like JPM, Uri, Ilya, Zireal, Apatryda, Erik, Nicolas, Jonathan and the others who I missed. They are the folks who use the library and uncovered gaps for the rest of us. Wei deserves extra thanks for providing the library and allowing us to move it forward. All failures should be directed at me.

Thanks to everyone who helped with the release, especially the folks who tolerated the extra testing.

Jeff

[nolo...@gmail.com]

Crypto++ 5.6.3 was released tonight. It can be downloaded from http://www.cryptopp.com/cryptopp563.zip.

The checksums are:

  * SHA-1: bd9fbe86ec1f3dd18ed395fae307da70dc86786f
  * SHA-256: bd72e1622e84d46664ca5fb331773e8c909d7861b8cdbdb269b27759cd2a8e89

The release can be checked out from Sourceforge at:

  * svn checkout https://svn.code.sf.net/p/cryptopp/code/trunk/c5 cryptopp-svn

And GitHub (preferred, as Sourceforge is going away next):

  * git clone https://github.com/weidai11/cryptopp.git cryptopp-git

It is tagged as CRYPTOPP_5_6_3 at both Sourceforge and GitHub.

Uri pointed out a missing header file in DSA class for the ZIP file. The tagged sources in Sourceforge and GitHub are OK.

The missing header did not show up under the self tests; rather it shows up in the field when the class was used. The missing header could cause a lot of problems for users in practice, and that's a problem we want to avoid.

We pushed a new 5.6.3 download. The updated checksums are:

  * SHA-1: c9f6febf22233e4e80c3cbde3469feadde8d6825
  * SHA-256: 77d5748071a4ef61c46302fd034cb90c6da1261d12d2c89bdcdfb297f1a9e2a3

Sorry about the confusion.

Jeff