Task #3924
closed
Reimplement util::Sha256 without cryptopp
Added by Alex Afanasyev almost 9 years ago.
Updated over 8 years ago.
Description
Current implementation is based on CryptoPP, which should be replaced with security::transform::digestFilter.
- Description updated (diff)
This is impossible as a non-breaking change, because the template parameter comes from CryptoPP.
- Subject changed from Refactor util::Digest to use transform::digestFilter to Refactor util::Sha256 to use transform::digestFilter
- Assignee set to Davide Pesavento
- Blocks Task #3886: Remove util::Digest class template added
- Blocks Task #3946: Get rid of cryptopp dependency added
- Status changed from New to In Progress
There does not seem to be a clean way to implement Sha256 using the security::transform framework. The former is inherently incremental, whereas a transform chain expects all its input to be available in one go and when the input is exhausted the digest gets finalized.
Any ideas?
- Subject changed from Refactor util::Sha256 to use transform::digestFilter to Reimplement util::Sha256 without cryptopp
- Status changed from In Progress to Code review
- % Done changed from 0 to 100
- Status changed from Code review to Closed
Also available in: Atom
PDF
Updated by 
Updated by