You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 text was updated successfully, but these errors were encountered:
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 Hasher class members though.
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 text was updated successfully, but these errors were encountered: