Description of problem:
The version of libcrypto++ provided by EPEL for RHEL7 claims to implement the SHA-3 algorithm. However, it uses an out of date pre-release version which is not the algorithm standardised.
The algorithm seems to have been standardised in v5.6.4 whereas EPEL provides v5.6.2.
The fix should be to provide v5.6.4 or later instead.
Steps to reproduce:
This is easy to reproduce see https://stackoverflow.com/questions/51215190/incorrect-behaviour-generating-sha3-hash-with-cryptopp/51226825#51226825
Version-Release number of selected component (if applicable):
An empty string gives the incorrect hash
An empty string should give the hash A7FFC6F8BF1ED76651C14756A061D662F580FF4DE43B49FA82D80A4B80F8434A
I'm pretty sure there is an ABI break with the update from 5.6.2->5.6.4/5
Can you check using the f27 branch ?
FEDORA-EPEL-2019-209b03a8a4 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-209b03a8a4
Unfortunately, there is an ABI break with this version (as I said). But if breaking ABI, please at least ask for permission on epel sig.
But at this point it's questionable to keep a version that old. Best would to update to a modern version and rebuild dependencies.
cryptopp-5.6.5-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-209b03a8a4