hashcat Forum
hashcat wont bruteforce - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html)
+--- Forum: Old hashcat Support (https://hashcat.net/forum/forum-20.html)
+--- Thread: hashcat wont bruteforce (/thread-1956.html)

Pages: 1 2


hashcat wont bruteforce - DaaQ - 01-15-2013

Hi,

i try to bruteforce a simple hash (pw: test) and im use this command line:
./hashcat-cli32.bin -m 0 -a 3 --pw-min=4 --pw-max=4 hash.txt ?l
But i only get this output:
Initializing hashcat v0.42 by atom with 8 threads and 32mb segment size...

Added hashes from file hash.txt: 1 (1 salts)
Activating quick-digest mode for single-hash

NOTE: press enter for status-screen

Started: Tue Jan 15 10:55:45 2013
Stopped: Tue Jan 15 10:55:45 2013

Why hashcat wont crack the hash?


RE: hashcat wont bruteforce - K9 - 01-15-2013

http://hashcat.net/wiki/doku.php?id=brute_force_attack


RE: hashcat wont bruteforce - DaaQ - 01-15-2013

Ive also tried ./hashcat-cli32.bin -m 0 -a 3 hash.txt ?l?l?l?l but the result is the same


RE: hashcat wont bruteforce - Waffle - 01-15-2013

There's something fundamental wrong.

Try creating the hash with a known program, make it simple:

md5 -s "a"

for example.

If you can't crack that, then your distribution may be corrupt, or something equally strange. The program works just fine in brute force mode for me.


RE: hashcat wont bruteforce - blandyuk - 01-15-2013

DaaQ, post the hash your testing...


RE: hashcat wont bruteforce - DaaQ - 01-15-2013

d8e8fca2dc0f896fd7cb4cb0031ba249

Input.Mode: Mask (?l)
Index.....: 0/1 (segment), 26 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 26/26 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Input.Mode: Mask (?l?l)
Index.....: 0/1 (segment), 676 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 676/676 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Input.Mode: Mask (?l?l?l)
Index.....: 0/1 (segment), 17576 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 17576/17576 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Input.Mode: Mask (?l?l?l?l)
Index.....: 0/1 (segment), 456976 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 456976/456976 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Started: Tue Jan 15 22:15:03 2013
Stopped: Tue Jan 15 22:15:05 2013


RE: hashcat wont bruteforce - forumhero - 01-15-2013

that's not the correct md5 hash of the word "test"

it should be this:
098f6bcd4621d373cade4e832627b4f6


RE: hashcat wont bruteforce - DaaQ - 01-15-2013

Yep, same result here. Why echo test | md5sum isnt the correct hash? oO


RE: hashcat wont bruteforce - forumhero - 01-15-2013

use this command instead of echo: md5 -s "test"

works for me

./hashcat-cli64.app -a 3 md5.txt ?l?l?l?l

Initializing hashcat v0.42 by atom with 8 threads and 32mb segment-size...

Added hashes from file md5.txt: 1 (1 salts)
Activating quick-digest mode for single-hash

NOTE: press enter for status-screen

Input.Mode: Mask (?l)
Index.....: 0/1 (segment), 26 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 26/26 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Input.Mode: Mask (?l?l)
Index.....: 0/1 (segment), 676 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 676/676 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
Input.Mode: Mask (?l?l?l)
Index.....: 0/1 (segment), 17576 (words), 0 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: - plains, - words
Progress..: 17576/17576 (100.00%)
Running...: --:--:--:--
Estimated.: --:--:--:--
098f6bcd4621d373cade4e832627b4f6:test
All hashes have been recovered


RE: hashcat wont bruteforce - epixoip - 01-16-2013

(01-15-2013, 11:26 PM)DaaQ Wrote: Why echo test | md5sum isnt the correct hash? oO

because you did "echo test" instead of "echo -n test", which means you hashed "test\n" instead of "test"