Differences between MD5 and SHA1 hash digests Endianness #57
Labels
No labels
announcement
bug
duplicate
enhancement
help wanted
invalid
Next release
question
sighting
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-intel/isa-l_crypto#57
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As part of using both MD5 and SHA1 hashes in our project it seems that there is a difference in the Endianness between them: it seems that digest words for SHA1 are big-endian, while MD5 ones are little-endian.
Is that really the case? and if so, why? as we want to use the same code for both it caused it to fail constantly for SHA1
The change we needed to add in our code
github.com/noobaa/noobaa-core@540d5e587a/src/native/tools/ssl_napi.cpp (L137)Yes, sorry for the inconsistency but you are correct. Looking at the code in ssl_napi.c, does hashing always go through the submit_and_flush() function? If so, you may not be getting the possible throughput improvement if you can maintain multiple outstanding jobs. I only looked at the
Hasherclass members though.Hey @gbtucker
You're right - we still use a single buffer in our code.
See here for context https://github.com/intel/isa-l_crypto/issues/45#issuecomment-638277664
Oh, didn't realize they were linked. Let me know if I can help with multi-flight.