Hashdeep: diferència entre les revisions

De WikiMar
Salta a la navegació Salta a la cerca
Línia 35: Línia 35:




*"Known file not used": file that disappeared
*"No match": new file added
*"Moved from": file renamed/moved from folder


MAN: http://md5deep.sourceforge.net/hashdeep.html
MAN: http://md5deep.sourceforge.net/hashdeep.html
More info: https://linhost.info/2010/05/using-hashdeep-to-ensure-data-integrity/
More info: https://linhost.info/2010/05/using-hashdeep-to-ensure-data-integrity/

Revisió del 15:24, 24 gen 2016


Create hash file

cd folder1
hashdeep -r -l . > hashdeep_$(date +%y%m%d).txt
  • -r Recursive mode
  • -l relative file paths
  • -e Estimate time (optional)

To get a deterministic order, use -j0 which disables multithreading (see the man page)

Verify hash on the same or another folder

List new files or changed (not missing files)

cd folder2
hashdeep -r -l -X -k hashdeep_$(date +%y%m%d).txt .
  • -r Recursive mode
  • -l relative file paths
  • -X Negative matching (only list differences): Only those files NOT in the list of known hashes are displayed. Display each failed hash that does not match the list of known hashes
  • (-v Verbose mode, it does nothing?)
  • -k Load list of known hashes
  • hashdeep.txt File containing hashes
  • dir Name of the directory in question

List how the files have been moved, new files and changed (slower)

cd folder2
hashdeep -r -l -avv -k hashdeep_$(date +%y%m%d).txt .
  • -a audit mode: Each input file is compared against the set of knowns. An audit is said to pass if each input file is matched against exactly one file in set of knowns. Any collisions, new files, or missing files will make the audit fail
  • -vv More verbose mode (display list of files missing, new files and changed files)
    • -vvv More verbose mode (also list files that are OK)


  • "Known file not used": file that disappeared
  • "No match": new file added
  • "Moved from": file renamed/moved from folder

MAN: http://md5deep.sourceforge.net/hashdeep.html More info: https://linhost.info/2010/05/using-hashdeep-to-ensure-data-integrity/