 |
Affects only 2018.3 i386 release... https://images.offensive-security.com/virtual-images/kali-linux-2018.3-vm-i386.7z 84715b351460cadad7e5d87e4034bfc50a9befc3904205bc6ca0afc6def61066 kali-linux-2018.3-vm-i386.7z and is reproducible with and without latest updates. |
 |
Thank you for your interest in Kali but this bug report is not actionable. |
|
|
Yes, the kali-linux-2018.3-i386.iso is also affected. I tested back on 2018.2-i386.iso which doesnt have this bug and cracks the password correctly. To reproduce start the live iso and use hashcat to crack the wordpress saltet md5 from the ticket. echo "\$P\$B9wJdX0NkO95U2L.kqAGXsFufwSp5N1" > wp.txt The output is not as expected and giving a hex'd output which is unusal. Please try exactly with the hash from issue 1683 posted in the description. Can you reproduce the issue now? |
|
|
Another user reported the bug exists in Kali Linux x86! https://github.com/hashcat/hashcat/issues/1695 From the testings this seems to be buggy since all updated x86 kernels since > 4.15.0-kali2-686-pae (2018.2), because the live iso still works correctly. Can you reproduce this as issue and tell us if it is related to kali x86 kernel or to hashcat or even anything else on your distro? Hashcat itself cracks the password correctly in 64bit releases in every version. In my opinion it is actionable now. |
 |
I reproduced this error with a simple plaintext md5 crack, on i686 virtualized environment, including fresh-download of live cd and 32bit prepared vm vbox download from offensive-security.com. Report here: https://github.com/hashcat/hashcat/issues/1709 tested with the following isos:
|
|
|
Some updates on the issue from Jens Steube: https://github.com/hashcat/hashcat/commit/a4ac370496d030777a5d5d65a894ac6bc2f953c6 It will get fixed by the next release of hashcat. In the meantime we are advised to use the latest commit. Thank all of you guys for contributing. |
|
|
fixed in version 5.0.0-1 in kali-rolling |
- Anonymous
