Hi Everyone,

Crypto++ 8.2 was released today. The 8.2 release was a minor, unplanned 
release. There are no CVEs or memory errors.

Two bugs were cleared that could cause discomfort for users. First, PowerPC 
switched from Power7 to Power8 for unaligned loads and stores. The bug 
affected Debian users on some PowerPC machines. Second, SHAKE-128 and 
SHAKE-256 constructors were fixed. The bug affected older GCC and some 
other compilers.

The release notes and list of issues fixed can be found at 
http://www.cryptopp.com/release820.html. The 8.2.0 ZIP archive can be 
downloaded from http://www.cryptopp.com/cryptopp820.zip. A GPG signature 
can be downloaded from http://www.cryptopp.com/cryptopp820.zip.sig.

The checksums for the 8.2.0 ZIP archive are:

  * SHA1: b042d2f0c93410abdec7c12bcd92787d019f8da1
  * SHA256: 03f0e2242e11b9d19b28d0ec5a3fa8ed5cc7b27640e6bed365744f593e858058
  * SHA512: 
753513a4ec8dd0fff2f551853ce6bd265d82219c28b033565b565b5e567fbee17adb419f4cde58a97e62b7d6533f4099aa4996cd0ba4775c6a2e7ae63a879da5
  * BLAKE2b: 
67aa850b887ae7aa869c9485bb18784492f6eec6cb12bf7c7cf84c776731eabf3c31965b47a60287e4e5a79dd3e9f0928dcfb185a0010a76f7cb96d2c3e8c6ae
  * WHIRLPOOL: 
7f7f67e22412dc2fd988c494a01fb463b863f83f497d37a35e40bc81dc2b4a46902581a896554c383804258b4c8fc158d2072aa28aa7e907aea72cc6e7cd8810

The 8.2.0 sources can be checked out from GitHub using the following. It is 
tagged as CRYPTOPP_8_2_0 at GitHub.

  * git clone http://github.com/weidai11/cryptopp.git cryptopp

There are 13 outstanding issues. Most of them are feature requests and 
enhancements.

Thanks to everyone who made it happen.

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.

Reply via email to