Always exhausted - with correct password and correct handshake - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html) +--- Forum: Old oclHashcat Support (https://hashcat.net/forum/forum-38.html) +--- Thread: Always exhausted - with correct password and correct handshake (/thread-5131.html) Pages:
1
2
|
RE: Always exhausted - with correct password and correct handshake - Millenium251 - 01-31-2016 (01-31-2016, 04:28 PM)Xanadrel Wrote: Just to make sure, you don't have any whitespace aside "hashcat!" in your file ? No white space there. With your new command line same result as before: Session.Name...: cudaHashcat Status.........: Exhausted Input.Mode.....: Mask (hashcat! ) [9] Hash.Target....: hashcat.net (00:25:cf:2d:b4:89 <-> b0:48:7a:d6:76:e2) Hash.Type......: WPA/WPA2 Time.Started...: 0 secs Time.Estimated.: 0 secs Speed.GPU.#1...: 0 H/s Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts Progress.......: 1/1 (100.00%) Rejected.......: 0/1 (0.00%) HWMon.GPU.#1...: 0% Util, 42c Temp, 0rpm Fan Started: Sun Jan 31 15:46:49 2016 Stopped: Sun Jan 31 15:46:51 2016 Update: I've use the return button and than i save the password, and it works: hashcat.net:0025cf2db489:b0487ad676e2:hashcat! Session.Name...: cudaHashcat Status.........: Cracked Input.Mode.....: Mask (hashcat!) [8] Hash.Target....: hashcat.net (00:25:cf:2d:b4:89 <-> b0:48:7a:d6:76:e2) Hash.Type......: WPA/WPA2 Time.Started...: 0 secs Speed.GPU.#1...: 0 H/s Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts Progress.......: 1/1 (100.00%) Rejected.......: 0/1 (0.00%) HWMon.GPU.#1...: 1% Util, 43c Temp, 0rpm Fan Started: Sun Jan 31 15:48:08 2016 Stopped: Sun Jan 31 15:48:09 2016 How I make sure that there is no white space in password.lst? I have billions of words in my lists . And the output.file doenst works. If the password is cracked, the output-text-file is blank. No password shown. RE: Always exhausted - with correct password and correct handshake - rico - 02-01-2016 The password would've be written to cudaHashcat.pot unless you've specified a session name or "-o oufilename" in your command. |