Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why on the same machine computing the SHA-1 hash of the same file produces two completely different SHA-1 hashes in windows and inside a msysgit Git bash?
Doesn’t the SHA-1 algorithm was intended to produce the same hash for the same file in all OSes?
On windows (with HashCheck):
File hello.txt
22596363b3de40b06f981fb85d82312e8c0ed511
Inside a msysgit’s Git bash windows (same machine, same file):
$ git hash-object hello.txt
3b18e512dba79e4c8300dd08aeb37f8e728b8dad
Git adds a header (“blob “, the length, then null) before calculating the SHA-1. See this blog post for how to emulate the calculation outside git.