| 2017-05-27 08:17:47 |
Andreas Moog |
description |
Testing with an approximately 10 gigabyte file, I have found multi-megabyte changes reflect with gtkhash's sha512 but not with hashrats' sha512 or jh512.
1.6.3 hashrat
Drawing from 16.04 Xenial packages |
Testing with an approximately 10 gigabyte file, I have found multi-megabyte changes reflect with gtkhash's sha512 but not with hashrats' sha512 or jh512.
1.6.3 hashrat
Drawing from 16.04 Xenial packages
To reproduce:
$ fallocate -l 10G sha512test
$ sha512sum sha512test
0a9ed4396868700784918a83a595845d70e582eb0e625c48ace24f4ee94e705247e210339c5f5a55e597f00d2c3217b0c0797e1bfc617161e00de96eaee2d068 sha512test
$ hashrat -sha512 sha512test
hash='sha512:cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e' type='file' mode='100644' uid='1000' gid='1000' size='10737418240' mtime='1495871799' inode='12058626' path='sha512test'
$ echo 1 >> sha512test
$ sha512sum sha512test
ae6565b7a9761d6524262738fe252121393aa3fc4987794f5f10175407e212ca81cf04edca949b0316947342e85eca4902dbd445cd53b703c316e5b2979cc976 sha512test
$ hashrat -sha512 sha512test
hash='sha512:cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e' type='file' mode='100644' uid='1000' gid='1000' size='10737418242' mtime='1495871852' inode='12058626' path='sha512test' |
|
