03-14-2013, 03:30 PM
Interesting twist. I fired up my Windows 2012 server (64bit) and ran the 64 bit version of hashcat. (hashcat-cli64)
64 bit results
==========
PS C:\Users\administrator\Documents> .\hashcat-cli64.exe -m 1800 hash dict
Initializing hashcat v0.43 by atom with 8 threads and 32mb segment-size...
Added hashes from file hash: 1 (1 salts)
Activating quick-digest mode for single-hash with salt
NOTE: press enter for status-screen
$6$DNRlEKWm$tEcdDjEuxYJFaA41eq1Ro4SHot3ov3SHeLo4LQqKNtzjHCNExT5kED8KpIGzQZrt758sa/WwCnQsgRS80EHRT/:123456
All hashes have been recovered
32 bit results
==========
BTW, the hash and dict files were also tested using the 32bit version of the hashcat utility with these results:
root@bt:~# cat dict
123456
root@bt:~# cat hash
$6$DNRlEKWm$tEcdDjEuxYJFaA41eq1Ro4SHot3ov3SHeLo4LQqKNtzjHCNExT5kED8KpIGzQZrt758sa/WwCnQsgRS80EHRT/
root@bt:~# ./tools/hashcat-0.43/hashcat-cli32.bin -m 1800 hash dict
Initializing hashcat v0.43 by atom with 8 threads and 32mb segment-size...
Added hashes from file hash: 1 (1 salts)
Activating quick-digest mode for single-hash with salt
NOTE: press enter for status-screen
Input.Mode: Dict (dict)
Index.....: 1/1 (segment), 1 (words), 7 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 1/1 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Started: Thu Mar 14 14:27:38 2013
Stopped: Thu Mar 14 14:27:39 2013
Conclusion
========
As suggested in the previous post, the 32 bit version of hashcat 0.43 seems to be affected. 64 bit works just fine. The commandline option --hash-type is still not functioning, however. (--hash-mode works just fine, but that is not the option name specified in the --help text.)
64 bit results
==========
PS C:\Users\administrator\Documents> .\hashcat-cli64.exe -m 1800 hash dict
Initializing hashcat v0.43 by atom with 8 threads and 32mb segment-size...
Added hashes from file hash: 1 (1 salts)
Activating quick-digest mode for single-hash with salt
NOTE: press enter for status-screen
$6$DNRlEKWm$tEcdDjEuxYJFaA41eq1Ro4SHot3ov3SHeLo4LQqKNtzjHCNExT5kED8KpIGzQZrt758sa/WwCnQsgRS80EHRT/:123456
All hashes have been recovered
32 bit results
==========
BTW, the hash and dict files were also tested using the 32bit version of the hashcat utility with these results:
root@bt:~# cat dict
123456
root@bt:~# cat hash
$6$DNRlEKWm$tEcdDjEuxYJFaA41eq1Ro4SHot3ov3SHeLo4LQqKNtzjHCNExT5kED8KpIGzQZrt758sa/WwCnQsgRS80EHRT/
root@bt:~# ./tools/hashcat-0.43/hashcat-cli32.bin -m 1800 hash dict
Initializing hashcat v0.43 by atom with 8 threads and 32mb segment-size...
Added hashes from file hash: 1 (1 salts)
Activating quick-digest mode for single-hash with salt
NOTE: press enter for status-screen
Input.Mode: Dict (dict)
Index.....: 1/1 (segment), 1 (words), 7 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 1/1 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Started: Thu Mar 14 14:27:38 2013
Stopped: Thu Mar 14 14:27:39 2013
Conclusion
========
As suggested in the previous post, the 32 bit version of hashcat 0.43 seems to be affected. 64 bit works just fine. The commandline option --hash-type is still not functioning, however. (--hash-mode works just fine, but that is not the option name specified in the --help text.)