Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: Errorless Error - cudaHashcat64
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi there. I'm looking for help with this 'errorless' error. Here is a quick overview of what is happening:

Code:
>cudaHashcat64 -m 2711 hash.txt realuniq.lst -o cracked.txt --gpu-accel 64 --gpu-loops 128
cudaHashcat v1.01 starting...

Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Early-Skip
* Not-Iterated
* Single-Hash
* Single-Salt
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: GeForce GTX 675M, 2048MB, 1240Mhz, 8MCU
Device #1: Kernel ./kernels/4318/m2710_a0.sm_21.64.ptx
Device #1: Kernel ./kernels/4318/bzero.64.ptx

Cache-hit dictionary stats realuniq.lst: 15696118781 bytes, 1196843344 words, 11
96843344 keyspace

[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>

Session.Name...: cudaHashcat
Status.........: Aborted
Input.Mode.....: File (realuniq.lst)
Hash.Target....: [I HAVE READ THE RULES - THEREFORE, REDACTED]

Hash.Type......: [REDACTED]
Time.Started...: Sat Mar 08 17:44:06 2014 (6 secs)
Time.Estimated.: Sat Mar 08 17:50:36 2014 (6 mins, 23 secs)
Speed.GPU.#1...:  8281.6 kH/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 18634642/1196843344 (1.56%)
Rejected.......: 153490/18634642 (0.82%)
HWMon.GPU.#1...: 13% Util, 64c Temp, N/A Fan

Started: Sat Mar 08 17:44:06 2014
Stopped: Sat Mar 08 17:44:13 2014

The multiple instances of "[s]tatus [p]ause [r]esume [b]ypass [q]uit =>" is where I press 'r' in an attempt to get it working, but I end up pressing 'q' on the last one.
I have already ran the time-out patch.
I use realuniq.lst from here: https://crackstation.net/buy-crackstatio...ionary.htm

Any help is appreciated.
So if it's not that obvious for the prompt:

Quote:[s]tatus [p]ause [r]esume [b]ypass [q]uit =>

[s]tatus : get the current status/progress for the attack
[p]ause : pause the attack
[r]esume : resume a paused attack
[b]ypass : skip the current wordlist/mask
[q]uit : stops the attack (abort)

So doing multiple 'r' when you never used 'p' is useless.
(03-08-2014, 07:55 PM)Xanadrel Wrote: [ -> ]So if it's not that obvious for the prompt:

Quote:[s]tatus [p]ause [r]esume [b]ypass [q]uit =>

[s]tatus : get the current status/progress for the attack
[p]ause : pause the attack
[r]esume : resume a paused attack
[b]ypass : skip the current wordlist/mask
[q]uit : stops the attack (abort)

So doing multiple 'r' when you never used 'p' is useless.
I wouldn't have posted this thread if I didn't try all the prompts. Nevertheless, let me try it again:
[Image: 9c15M1v.png]

Bypass just bypasses the only wordlist, thus exhausting the cracking process.

There's no way to break this loop of neverending prompts. How can I avoid this?
Quote:There's no way to break this loop of neverending prompts. How can I avoid this?

Stop pressing keys...
It's a prompt, like any windows/linux one, you input commands, it executes them.
(03-08-2014, 08:02 PM)Xanadrel Wrote: [ -> ]
Quote:There's no way to break this loop of neverending prompts. How can I avoid this?

Stop pressing keys...
It's a prompt, like any windows/linux one, you input commands, it executes them.

Oh, so this isn't an error? I thought the prompt was there to catch an error and asked me whether I wanted to proceed or stop the process. Thanks for your help.