02-13-2021, 11:21 AM
(This post was last modified: 02-13-2021, 11:29 AM by mailmuncher2000.)
It seems like hashcat v6.1.1 is still using the masked hash logic for SHA1 (-m 100 ) which should probably be marked as bug. That is to say that hashcat seems to be ignoring the first 5 nibbles of the SHA1 hash while checking (potential bug?)
SHA1(testing123) = 4c0d2b951ffabd6f9a10489dc40fc356ec1d26d5
But hashcat will find this hash for testing123:
hashcat -m 100 -a3 00000b951ffabd6f9a10489dc40fc356ec1d26d5 testing?d?d?d
00000b951ffabd6f9a10489dc40fc356ec1d26d5:testing123
Please can someone report this as a bug? Unless it is considered a feature?
SHA1(testing123) = 4c0d2b951ffabd6f9a10489dc40fc356ec1d26d5
But hashcat will find this hash for testing123:
hashcat -m 100 -a3 00000b951ffabd6f9a10489dc40fc356ec1d26d5 testing?d?d?d
00000b951ffabd6f9a10489dc40fc356ec1d26d5:testing123
Please can someone report this as a bug? Unless it is considered a feature?