I'm planning to release Crypto++ 5.1 in a few days. It is a maintainance
release with mostly bug fixes. Before I make the release I would
like to know if anyone is using DLIES in DHAES mode, or RW/EMSA2 signature
scheme, because I found standard conformance bugs in these
implementations, and the fixes I put in are not backwards (bugwards?)
compatible. If anyone is using them, I'll consider putting in additional
classes that will implement them in the old non-standard ways.
Here are the changes from 5.0:
5.1 - added PSS padding and changed PSSR to track IEEE P1363a draft standard
- added blinding for RSA and Rabin to defend against timing attacks
on decryption operations (required API changes for decryption)
- fixed a bug in CBC and ECB modes with processing non-aligned data
- fixed standard conformance bugs in DLIES (DHAES mode) and RW/EMSA2
signature scheme (these fixes are not backwards compatible)
- fixed a number of minor bugs and portability problems
- removed Sapphire
