Logical File hash mismatch
I have a PST file which was provided, i hashed the file using the same tool client used which is HashmyFiles but received a different MD5 and SHA1. What could be the possible reason? The data was provided via SFTP and the PST was exported from Office365 via the standard method by the client.
A single bit difference will produce a completely different hash. ie the file has been changed. This is all a different hash value can tell you.
A simple explaination would be if the file was padded in transmission - check if the length is identical
pst is a data storage file used by the microsoft outlook and exchange. it mostly contains personal info and mail correspondence and also has the size limitation of 2GB. please check the size of the file at the origination and reciepient end. during transmission any truncation happens, there will be mismatch of hash. hash is very sensitive algorithm even a minute change in the file changes the hash.
For more than 40 years FTP has been corrupting files.
People pick the wrong file transfer mode (ASCII / binary) and this leaves the file corrupted after the transfer.
Thanks for the reply guys; i'll have a look on their client ends and see if any changes were made.
Also check that no-one has accessed the PST in the interim, even opening it in Outlook (or any other application) will change the has even if nothing was added or deleted