-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Ability to recursively hash folders, sub-folders, and their contents #143
Comments
Much needed a feature as more often we need to see the hash values of the full content in subfolders too. Also be great if we can see the file size, last updated & file created DateTime stamps on the result list, with the ability to sort the list according to any of the list headers. |
As nice as that would be, I question if that'd be able to be implemented without breaking compatibility with other software that can read .sfv and .sha1 checksum files. EDIT: Unless this information was stored in the equivalent of a comment? Other software seem to treat lines beginning with |
As it currently stands, GtkHash is not able to hash the contents of folders and/or sub-folders, only multiple individual files. Including this would then replicate the functionality that exists in "HashCheck Shell Extension" (which I personally have used for over a decade now...but as of a few months ago, I am no longer using Windows on my primary PC).
And, just like how one can do a right-click -> "open with" and open a file directly in GtkHash and have it automatically hashed, one should ideally be able to do the same sort of right-click -> "open with" on a folder and have it opened in in GtkHash directly and subsequently automatically start hashing its contents (though, at least on Linux Mint 20.3, the right-click -> "open with" is only present within Thunar or Nemo windows and isn't available on the desktop itself).
Also, as mentioned in my other issue, "HashCheck Shell Extension" actually works via WINE 7.x, at least for reading/verifying/processing already-existing checksum files.
Here are some examples of the format used by "HashCheck Shell Extension" when folders and sub-folders are involved:
CRC32
SHA1
Do note that, despite the presence of asterisks in the SHA1 example, they seem to actually be optional and it similarly works without issue even if the asterisks are not present. For reference, not having an asterisk is how GtkHash currently behaves when saving checksum files and therefore, in theory, that aspect doesn't actually require any change.
EDIT: It seems like GtkHash only supports reading checksum files that use a normal slash as a directory separator rather than also a backslash. That's a bit of an issue since the slew of Windows software for make checksum files create paths with backslashes (and obviously they're the only solution at this time for GUI-based checksum creation supporting recursive directories).
The text was updated successfully, but these errors were encountered: