Crypto++ 5.6.3 Release Candidate available (RC4)

60 views
Skip to first unread message

Jeffrey Walton

unread,
Oct 5, 2015, 11:32:36 AM10/5/15
to Crypto++ Users
Hi Everyone,

We have an RC4 available at http://www.cryptopp.com/cryptopp563rc4.zip. Here are the checksums:

  $ md5sum cryptopp563rc4.zip
  9a1e7288de1de683286e96a7f9c1dfe2
  $ sha1sum cryptopp563rc4.zip
  23e47dc6db6df0007b6bc6828e6ce288b68066ea
  $ sha256sum cryptopp563rc4.zip
  33c1e973d4114589620ac47fc8fc2818417d0f6e901eb3df86fd3673fa5d1ab8

**********

Three warnings have been introduced in the makefile to help ensure a well configured library. If you encounter them (you likely will due to versioning requirements), then please visit https://cryptopp.com/wiki/Config.h#Recommendations for a discussion.

$ make
WARNING: CRYPTOPP_NO_UNALIGNED_DATA_ACCESS is not defined in config.h
WARNING: CRYPTOPP_INIT_PRIORITY is not defined in config.h
WARNING: CRYPTOPP_MAINTAIN_BACKWARDS_COMPATIBILITY_562 is defined in config.h
g++ -DNDEBUG -g2 -O2 -fPIC -march=native -pipe -c cryptlib.cpp
...

The most important one is CRYPTOPP_MAINTAIN_BACKWARDS_COMPATIBILITY_562. If possible, you should comment it out or delete it all together. You should do so because it harbors undefined behavior. (The UB cannot be removed unless ABI and binary compatibility are broken).

Unaligned data access also harbors undefined behavior, so you should ensure CRYPTOPP_NO_UNALIGNED_DATA_ACCESS is defined.

**********

There's a crash in SHA on iOS when building from the command line. Its currently being investigated. Its being tracked at https://github.com/weidai11/cryptopp/issues/37 .

Jeff

ra...@teamviewer.com

unread,
Oct 6, 2015, 4:21:53 AM10/6/15
to Crypto++ Users
Am Montag, 5. Oktober 2015 17:32:36 UTC+2 schrieb Jeffrey Walton:

We have an RC4 available at http://www.cryptopp.com/cryptopp563rc4.zip.


There's a compilation error with Visual C++ 2015 because in trdlocal.cpp, the constructor of ThreadLocalStorage is marked as CRYPTOPP_THROW instead of the destructor. Apart from that, everything works perfectly for me with Visual C++ 2013 and 2015, both 32 and 64 bits, with CRYPTOPP_NO_BACKWARDS_COMPATIBILITY_562 and CRYPTOPP_NO_UNALIGNED_DATA_ACCESS defined.

Marcel

Jeffrey Walton

unread,
Oct 6, 2015, 9:48:24 AM10/6/15
to Crypto++ Users

Thanks Marcel. Uri mentioned it too. It will be cleared at release.

I encountered it myself, but I only fixed it on local copies of the library on Debian and Fedora. I did not migrate it back to the copy I use to build the ZIP. Sorry about that.

The defines are just plain awkward for 5.6.3. At 6.0, we can break compatibility, so they won't be an issue.

Jeff

Jean-Pierre Münch

unread,
Oct 11, 2015, 3:47:12 PM10/11/15
to cryptop...@googlegroups.com
I've found a small bug, that causes a build error on VS2015.

You define "ThreadLocalStorage::~ThreadLocalStorage() CRYPTOPP_THROW;" and implement "ThreadLocalStorage::~ThreadLocalStorage()" which VS sees as two different declarations and errors on this, the fix is to add the CRYPTOPP_THROW in the source file as well.

I hope I didn't miss someone else reporting this :)

BR

JPM

Jeff
--
--
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-user...@googlegroups.com.
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 cryptopp-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages