No password in outfile? - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html) +--- Forum: Very old oclHashcat Support (https://hashcat.net/forum/forum-21.html) +--- Thread: No password in outfile? (/thread-471.html) |
No password in outfile? - fugazix - 09-07-2011 Hi I'm trying to crack my own Mac OS 10.6 password using a password hash extracted from my shadow file and a dict file containing only my password. Everything seems to go fine and oclhashcat reports that my password has been cracked but the password does not appear in my outfile. my hash in in the file sha.txt and looks like this: 775DE041552B7FC10421B0288965F69C9544B70A:9001B23E I run the command: ./cudaHashcat64.bin -m 102 --hex-salt sha.txt dict.txt dict.txt --outfile-format=2 -o output.txt terminal output: cudaHashcat v0.26 by atom starting... Digests: 1 entries, 1 unique Salts: 1 entries, 1 unique Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes Platform: NVidia compatible platform found Watchdog: Temperature limit set to 90c Device #1: GeForce GTX 275, 895MB, 1419Mhz, 30MCU NOTE: gpu-accel auto-adjusted to: 1 Device #1: Kernel ./kernels/4318/m0102.sm_13.64.cubin WARNING: words in dict_left < 7680. Can't gain full performance WARNING: words in dict_right < 128. Can't gain full performance [s]tatus [p]ause [r]esume [q]uit => Status.......: Cracked Hash.Type....: sha1($salt.$pass) Mode.Left....: Dict 'dict.txt' (7) Mode.Right...: Dict 'dict.txt' (7) Speed.GPU*...: 52.0k/s Recovered....: 1/1 Digests, 1/1 Salts Progress.....: 0/49 (0.00%) Running......: 1 sec Estimated....: 0 secs HW.Monitor.#1: 0% GPU, 70c Temp Started: Wed Sep 7 15:05:11 2011 Stopped: Wed Sep 7 15:05:12 2011 And the contents of my outfile: 775de041552b7fc10421b0288965f69c9544b70a:9001b23e:: I've tried changing the outfile format to no avail. What's going wrong here? RE: No password in outfile? - atom - 09-07-2011 maybe a bug, pls paste content of dict.txt RE: No password in outfile? - fugazix - 09-08-2011 I tried the same thing with another password, same result: $ ./cudaHashcat64.bin -m 102 --hex-salt testhash/hash.txt testhash/pass.txt testhash/pass.txt --outfile-format=2 -o out.txt cudaHashcat v0.26 by atom starting... Digests: 1 entries, 1 unique Salts: 1 entries, 1 unique Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes Platform: NVidia compatible platform found Watchdog: Temperature limit set to 90c Device #1: GeForce GTX 275, 895MB, 1419Mhz, 30MCU NOTE: gpu-accel auto-adjusted to: 1 Device #1: Kernel ./kernels/4318/m0102.sm_13.64.cubin WARNING: words in dict_left < 7680. Can't gain full performance WARNING: words in dict_right < 128. Can't gain full performance [s]tatus [p]ause [r]esume [q]uit => Status.......: Cracked Hash.Type....: sha1($salt.$pass) Mode.Left....: Dict 'testhash/pass.txt' (1) Mode.Right...: Dict 'testhash/pass.txt' (1) Speed.GPU*...: 0/s Recovered....: 1/1 Digests, 1/1 Salts Progress.....: 0/1 (0.00%) Running......: 1 sec Estimated....: 0 secs HW.Monitor.#1: 0% GPU, 69c Temp Started: Wed Sep 7 19:16:14 2011 Stopped: Wed Sep 7 19:16:16 2011 contents of hash.txt Quote:91401728B61BCF61BB572616261C8B09B258384E:927E2D11 contents of pass.txt Quote:q1w2e3r4t5 result in out.txt Quote:91401728b61bcf61bb572616261c8b09b258384e:927e2d11:: I also get the same result when omitting -o RE: No password in outfile? - atom - 09-08-2011 ok, cool. i can reproduce it. will fix it in the next version. thanks for reporting RE: No password in outfile? - atom - 09-08-2011 aww, i was to fast. i just saw your dictionary input contains a 10 char word. in combinations its 20 (so its to big). max supported combination length is 15. Quote:root@ht:~/oclHashcat-0.27# ./cudaHashcat64.bin -m 102 --hex-salt hash.txt q1w2e3r4t5 q1w2e3r4t5 RE: No password in outfile? - mastercracker - 09-09-2011 If the pass is q1w2e3r4t5 only then use the following command line to crack it: $ ./cudaHashcat64.bin -m 102 --hex-salt testhash/hash.txt -1 ?s?d?u?l testhash/pass.txt ?1 --rule-left="]" --outfile-format=2 -o out.txt |