Hello,
it seems that the value that start to lead to wrong values is 2048M.
Also the returned hash from there is always the same as for an empty file.
I first thought it has something to do with large file support, but it
looks like that is already enabled.
(gdb) print sizeof(off_t)
$1 = 8
Package: hashrat
Version: 1.8.3+dfsg-2
Priority: important
Hi there,
there's something wonky going on when using hashtag's sha512 hash for big
files (10 Gig in this case):
$ fallocate -l 10G sha512test
$ sha512sum sha512test
0a9ed4396868700784918a83a595845d70e582eb0e625c48ace24f4ee94e705247e210
2 matches
Mail list logo
