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
Hashdeep currently double reports changed files during an audit. If a file has changed, the program reports both "No match" for the new file and "Known file not used". For example:
$ ~/research/md5deep/hashdeep/hashdeep -vvak known -r tmp
/users/jessek/tmp/tmp/bar: No match
/users/jessek/tmp/tmp/bar: Known file not used
This should instead be reported as the file has changed. A 'new file found' should be reserved for a case when there was no file specified at the given path.
The text was updated successfully, but these errors were encountered:
Converted from SourceForge issue 2960381, submitted by jessekornblum
Hashdeep currently double reports changed files during an audit. If a file has changed, the program reports both "No match" for the new file and "Known file not used". For example:
$ ~/research/md5deep/hashdeep/hashdeep -vvak known -r tmp
/users/jessek/tmp/tmp/bar: No match
/users/jessek/tmp/tmp/bar: Known file not used
This should instead be reported as the file has changed. A 'new file found' should be reserved for a case when there was no file specified at the given path.
The text was updated successfully, but these errors were encountered: