bug in 1.35?

[rsberzerker]

I hadn't noticed 1.35 was out, so I just downloaded it. I have been using 1.33. But when I ran 1.35, it didn't recover anything, while the same run with 1.33 did. Here are the command lines.

First I ran 1.35:

Code:

C:\<snip>\hashlist>..\cudaHashcat-1.35\cudaHashcat64.exe -a 0 -m 0 --remove -o 32found.txt 32_left_split_5.txt ..\wordlists -r rules\best64.rule --session=5md5best64

Hashes recovered = 0

Then, without changing anything (other than cudahashcat version; I used command history and just changed the 5 to a 3), I ran 1.33:

Code:

C:\<snip>\hashlist>..\cudaHashcat-1.33\cudaHashcat64.exe -a 0 -m 0 --remove -o 32found.txt 32_left_split_5.txt ..\wordlists -r rules\best64.rule --session=5md5best64

Hashes recovered = 294

I repeated this with a different ruleset and got roughly the same results: 1.35 first - 0 recovered, then 1.33 - 6 recovered.

Is this a bug in 1.35 or did something change between 1.33 or 1.35?

[undeath]

https://hashcat.net/forum/thread-4264-po...l#pid24293

[epixoip]

Yes, -m 0 is broken in cudaHashcat 1.35. It's also broken in 1.31 - 1.33, though not as severely. Hoping 1.36 will be released real soon.

[rsberzerker]

So bug. Thanks. I guess I stick with 1.33 for now.