Exphash from sha256 to md5 to match imphash#377
Merged
erocarrera merged 1 commit intoerocarrera:masterfrom Jan 11, 2024
Merged
Conversation
Owner
|
I'm a bit torn in this case: I see the rationale in staying consistent with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #354 added exphash using the
sha256function instead ofmd5, which creates two issues:This PR proposes using
md5instead ofsha256for exphash to maintain consistency.Note: I believe this confusion stems from a discrepancy between the original blog post about exphash, which mentions the usage of
sha256, and its integration into public community projects.