Running rhash v1.3.0 stock win32 build under xp sp3.
There seems to be no warning that files were skipped due to, for example, sharing violations. I think there should be at least an option, if not the default, to report the files that could not be processed - instead of silently ignoring the error. For example, under windows, the %userprofile% directory has at least of two files ntuser.dat.* which are exclusively locked by the system at all times. Thus, it is not possible for rhash to open/hash them, but this should still be reported as a failure, rather than be silently ignored.
When target is a wildcard, rhash issues warnings (to stderr) for each subdirectory matching the wildcard. Don't think this is warranted, since that's not an error, and the user who entered the wildcard certainly meant "files" not "directories".
C:\tmp>rhash --md5 -- "%userprofile%\*.*"
RHash: H:\Documents and Settings\liviu\Application Data: Is a directory
13cfb479e23f335eb4f1f4a80602757a H:\Documents and Settings\liviu\ntuser.ini
9038e4d82beefb06d8a10c929ddedc70 H:\Documents and Settings\liviu\ntuser.pol
[... but there is no mention of ntuser.dat and ntuser.dat.log which couldn't be hashed ...]
RHash: H:\Documents and Settings\liviu\PrintHood: Is a directory
Log in to post a comment.