jessek
hashdeep without the hashing?
For testing purposes I'd like to be able to run hashdeep /without/ performing the hashsums, ie output only filepathname and size.
I can't see an option to do that: is it possible?
i
So basically, you want a NULL cipher, right?
On Nov 26, 2016, at 3:06 PM, IanWorthington [email protected] wrote:
For testing purposes I'd like to be able to run hashdeep /without/ performing the hashsums, ie output only filepathname and size.
I can't see an option to do that: is it possible?
i
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jessek/hashdeep/issues/362, or mute the thread https://github.com/notifications/unsubscribe-auth/ABhTrOhvHBITV_YtUf7TvqLVxXtIaHOcks5rCJFTgaJpZM4K8-so.
I'm not sure this is entirely useful, to be honest. It'd probably make more sense to use your system's integrated utilities to check for that instead of calling to an external program.
I can see the utility of this for testing hashdeep's directory traversal for problems while avoiding CPU-intensive computations, I suppose…
I implemented this in PR #364, but no guarantees since I don't know what I'm doing. ;)
If you're just testing directory traversal, you could use '-D 2' for level 2 debugging, and '-i 1' to only hash files of size 1 or less. Search the output for file-specific output such as 'dig_normal' and you'll see each file that's evaluated during directory traversal.
Interestingly, passing the -i option 0 just prints out "Requested size threshold implies not hashing anything." I'd like to see that check removed, as the following is a quick way to search for empty files: hashdeep -r . -i 0
Granted, that's what find(1) is for, but if I want to print the null hash next to every empty file, why block me?
