Actions
Task #3924
closedReimplement util::Sha256 without cryptopp
Start date:
Due date:
% Done:
100%
Estimated time:
Description
Current implementation is based on CryptoPP, which should be replaced with security::transform::digestFilter
.
Updated by Junxiao Shi almost 8 years ago
This is impossible as a non-breaking change, because the template parameter comes from CryptoPP.
Updated by Davide Pesavento over 7 years ago
- Subject changed from Refactor util::Digest to use transform::digestFilter to Refactor util::Sha256 to use transform::digestFilter
- Assignee set to Davide Pesavento
Updated by Davide Pesavento over 7 years ago
- Blocks Task #3886: Remove util::Digest class template added
Updated by Davide Pesavento over 7 years ago
- Blocks Task #3946: Get rid of cryptopp dependency added
Updated by Davide Pesavento over 7 years ago
See https://redmine.named-data.net/issues/3886#note-9 for some more background on the decision.
Updated by Davide Pesavento over 7 years ago
- 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?
Updated by Davide Pesavento over 7 years ago
- 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
Updated by Davide Pesavento over 7 years ago
- Status changed from Code review to Closed
Actions