0.42: Bugs

[M@LIK]

In this thread I'm going to share bugs that still exist in the current latest release of CPU's hashcat (0.42), their severity level and personal workaround if available. Feel free to join me pissing atom off.

Level: Non-critical.
Starting with the flag --hex-salt, as mentioned here: https://hashcat.net/forum/thread-1796.html it was implemented, but in live action it was more than just implementation:

Code:

NOTE: press enter for status-screen

38b3eff8baf56627478ec76a704e9b52:3130:1
All hashes have been recovered
38b3eff8baf56627478ec76a704e9b52:3130:1
All hashes have been recovered
38b3eff8baf56627478ec76a704e9b52:3130:1
All hashes have been recovered38b3eff8
baf56627478ec76a704e9b52:3130:1
All hashes have been recovered
38b3eff8baf56627478ec76a704e9b52:3130:1
38b3eff8baf56627478ec76a704e9b52All hashes have been recovered
:3130:1
All hashes have been recovered
38b3eff8baf56627478ec76a704e9b52:3130:1
38b3eff8baf56627478ec76a704e9b52:313All hashes have been recovered
0:1
All hashes have been recovered

As far as I know, this fuck-up only happens when --hex-salt meet up with -a3.
Workaround: Don't use it.

Moving on...
Level: Non-critical.
--hex-charset is mentioned in --help since 0.40, but turns out to be an "unknown option":

Code:

hc64 -a3 --hex-charset -1 30 hash ?1
hc64: unknown option -- hex-charset

Workaround: Don't use it.

To be continued...

NOTE: I posted this in the Beta section to keep thing a little private, and also, it's not cool for hashcat's reputation to report bugs right after a release. However, I'm ok with moving it the the right section.