sha1sum-sha1: sha256sum-sha256: question

[nod5]

1.5.0.1269a (x64)

I did not get commands sha1sum-sha1: and sha256sum-sha256: to work.

Search for files with the specified checksum file hash. Everything will search for a .sfv, .md5, .sha1 or .sha256 checksum file in the same location as the file being searched.

I tried all combinations of these.
checksum file name: filename.ext.sha1, filename.sha1
checksum file contents: "<hash> <filename>", "<hash> *<filename>"

What checksum filename and content format does Everything expect?

[void]

The filename of the .sfv, .md5, .sha1 or .sha256 file can be anything.
Everything will use the first .sfv, .md5, .sha1 or .sha256 file found.

SFV

SFV Example:

Code: Select all

; This is a comment
file_one.zip   c45ad668
file_two.zip   7903b8e6
file_three.zip e99a65fb

md5sum

md5sum Example:

Code: Select all

595f44fec1e92a71d3e9e77456ba80d1  filetohashA.txt
71f920fa275127a7b60fa4d4d41432a3  filetohashB.txt
43c191bf6d6c3f263a8cd0efd4a058ab  filetohashC.txt

sha1sum

sha1sum Example:

Code: Select all

65c23f142ff6bcfdddeccebc0e5e63c41c9c1721  file_s11
d3d59905cf5fc930cd4bf5b709d5ffdbaa9443b2  file_s21
5590e00ea904568199b86aee4b770fb1b5645ab8  file_02

[nod5]

Thanks. With the format "<hash><space><space><filename>" for the .sha1 file I can get 1.5 to find the matching file.

But I now encountered another issue: if I delete the .sha1 file Everything still shows the match for the search.
Example search:

C:\checksum\a.txt sha1sum-sha1:a94a8fe5ccb19ba61c4c0873d391e987982fbbd3

The file match lingers in the search results even if I clear the search string and enter it again. I have to rebuild the index to get Everything to notice that the .sha1 file is not present in the folder any longer.

[void]

Added:

The filename of the .sfv, .md5, .sha1 or .sha256 file can be anything.
Everything will use the first .sfv, .md5, .sha1 or .sha256 file found.



Press F5 to reload sfv, md5sum, sha1sum and sha256sum cache.

[nod5]

Press F5 to reload sfv, md5sum, sha1sum and sha256sum cache.

Ok. Yes after F5 press v1.5 does notice if the .sha256 file in/out of the test folder, though it still seems to not work all the time or with delay, but I can't yet pinpoint the issue more exactly.

To be fair I have so far only tested this feature a little just to check out what new things v1.5 can do and because of that I'm not clear on what use case you had in mind when adding that feature. I first thought the idea was to have one .sha256 etc file per hashed file. But now it sounds like the intended use is to have a single .sha256 that contains hash/filename pairs for all to-later-be-verified files in that folder. Correct?

[void]

The intention was to have a single .sfv, .md5, .sha1 file that contains hashes for all files in the directory.

Everything 1.5.0.1270a will now look in all .sfv, .md5, .sha1 or .sha256 files in the same location for the file hash.

[wrisco]

If you find the time I think it would be great to have support for more super-fast algorithms like xxHash and BLAKE3

[therube]

(xxHash has been mentioned a number of times.)