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.

[radix]

bugs are bugs regardless of when it was released. ill take a look and see wtfs up

what was your command line and the hashes? I cant reproduce this.

[M@LIK]

Well, let's just consider the "keep things a little private" part.

I assume you're talking about the --hex-salt bug.
Details:

Code:

H:
38b3eff8baf56627478ec76a704e9b52:3130
// "101" md5ed

hc64 -m20 -a3 --hex-salt ..\hash.txt ?d
// hashcat-cli64.exe is used

-a0 is just fine. -a3 is the problema.

[radix]

k, hex charset is fixed, let me see if i can unfuck the

[M@LIK]

Level: Non-critical.
hashcat adds something completely different than the actual hash to hashcat.pot.
Further details: https://hashcat.net/forum/thread-1789.html
Workaround: If you need them so badly, re-hash your passwords.

[atom]

Level: Non-critical.
hashcat adds something completely different than the actual hash to hashcat.pot.
Further details: https://hashcat.net/forum/thread-1789.html
Workaround: If you need them so badly, re-hash your passwords.

Hm, thought I fixed this. So its still in there?

[M@LIK]

Hm, thought I fixed this. So its still in there?

Yes, sir.

Level: Non-critical.
hashcat doesn't remove the hash using --remove parameter if it was only one hash and it was cracked.
Workaround: nul > hashfile.

Level: Complementary only
The following info should be added in .\docs\rules.txt:

Code:

#define RULE_OP_REJECT_LESS             '<'
#define RULE_OP_REJECT_GREATER          '>'
#define RULE_OP_REJECT_CONTAIN          '!'
#define RULE_OP_REJECT_NOT_CONTAIN      '/'
#define RULE_OP_REJECT_EQUAL_FIRST      '('
#define RULE_OP_REJECT_EQUAL_LAST       ')'
#define RULE_OP_REJECT_EQUAL_AT         '='
#define RULE_OP_REJECT_CONTAINS         '%'
#define RULE_OP_REJECT_MEMORY           'Q'

With their explanations and also the other new rules (M, X, 4, 6)

I know all of these are just minor matters, hardcore testing phase hasn't started yet. (I gotta study about ventilation-perfusion mismatch and shit @_@)

[M@LIK]

k, hex charset is fixed

hashcat-0.43b1:
Okay, it's a "known option" now, but:

Code:

hc64 -a3 --hex-charset -1 30 hash ?1
...
NOTE: press enter for status-screen

cfcfcccfcfcd208495d565ef66e7dff9f98764dacfcd208495d565ef66e7dff9f98764dafcd20849
5d565ef66e7dff9f98764da:0
cdcd208495d565ef66e7dff9f98764dafcd208495d565ef66e7dff9f98764dacd208495d565ef66e
7dfcf:0:0
:0
:All 208495d565ef66e7dff9f98764dahashes have All :0
f9All hashes
hashes have f98764dabeen All hashes been recoveredhave All hashes
have been been cd208495d565ef66e7dff9f98764darecoveredrecovered:0
recovered:0
hAll

ave 0
hasAll hashes
All have hes been been hashes have recoveredbeen recoveredrecovered

have
been recovered

Apperently, --hex-salt had sex with --hex-charset and transferred this STD.

OFF TOPIC:
@atom:: .\oclHashcat-lite-0.14b2\docs\changes.txt:

Code:

type: bug
file: host programs
desc: fixed bug in in case user specified to many wordlists or to long paths to wordlists

No wordlists in -lite.

[radix]

tha fuck

[M@LIK]

hashcat-0.43b3:
Level: Critical
hashcat is crashing instantly when using -a3.

Code:

hash = 00000000000000000000000000000000
hc64 -a3 hash ?d?d?d?d
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

NOTE: press enter for status-screen

Input.Mode: Mask (?d)
Index.....: 0/1 (segment), 10 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 10/10 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
// crash (... has stopped working)

However, there's no crash if all hashes have been recovered, there's the usual fuck-up, instead:

Code:

hash = cfcd208495d565ef66e7dff9f98764da
hc64 -a3 hash ?d?d?d?d
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

NOTE: press enter for status-screen

cfcfcd208495d565ef66e7dff9f98764dacd208495d565ef66e7dff9f98764da:0
:0All
hashes All have hashes been have recoveredbeen
recovered
// no crash