How Calculate GPU Cracking Time

How Calculate GPU Cracking Time - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: How Calculate GPU Cracking Time (/thread-6430.html)

Pages: 1 2

How Calculate GPU Cracking Time - Dot - 03-26-2017

Hi
is there a way to guess how many passwords in a wordlist my GPU can try?
i saw there is a benchmark option and speed only time
is it one of these?
meaning i want to know if i have a word list like rockyou and i tried it on an md5 hash how many passwords my PC can try in a second.

RE: How Calculate GPU Cracking Time - royce - 03-26-2017

The best way to do this is to perform an actual run.

Raw wordlist mode (with no rules) is very, very fast. hashcat's guessing speed is so fast that it can often spend more time caching a large dictionary than the actual guessing:

Code:
$ echo en 'hashcathashcat' | md5sum | awk '{print $1}'

38f63c3a621ad108457843529feec46a

$ ./hashcat -m 0 -a 0 -w 4 38f63c3a621ad108457843529feec46a really-big-wordlist.txt

hashcat (v3.40-74-g368f8b39) starting...

[snip showing interim progress]

Dictionary cache building really-big-wordlist.txt: 12822195310 bytes (81.69%)

[snip]

Dictionary cache built:

Filename..: really-big-wordlist.txt

Passwords.: 1212356398

Bytes.....: 15696118781

Keyspace..: 1196843344

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

Session..........: hashcat

Status...........: Exhausted

Hash.Type........: MD5

Hash.Target......: 38f63c3a621ad108457843529feec46a

Time.Started.....: Sun Mar 26 06:38:05 2017 (1 min, 6 secs)

Time.Estimated...: Sun Mar 26 06:39:11 2017 (0 secs)

[snip]

Started: Sun Mar 26 06:34:53 2017 (epoch: 1490510093)

Stopped: Sun Mar 26 06:39:14 2017 (epoch: 1490510354)

Dictionary caching: 143s (54.79% - 2 mins, 23 secs)
Other setup: 52s (19.92% - 52 secs)
Total setup: 195s (74.71% - 3 mins, 15 secs)
Guessing: 66s (25.29% - 1 min, 6 secs )
Total time: 261s (4 mins, 21 secs)

Side note: the stats above are not part of hashcat's output, but they might be useful for others, so I've requested them as a feature.

RE: How Calculate GPU Cracking Time - atom - 03-27-2017

You're looking for --speed-only

RE: How Calculate GPU Cracking Time - Dot - 03-28-2017

(03-26-2017, 05:36 PM)royce Wrote: The best way to do this is to perform an actual run.

Raw wordlist mode (with no rules) is very, very fast. hashcat's guessing speed is so fast that it can often spend more time caching a large dictionary than the actual guessing:

Code:
$ echo en 'hashcathashcat' | md5sum | awk '{print $1}' 38f63c3a621ad108457843529feec46a $ ./hashcat -m 0 -a 0 -w 4 38f63c3a621ad108457843529feec46a really-big-wordlist.txt hashcat (v3.40-74-g368f8b39) starting... [snip showing interim progress] Dictionary cache building really-big-wordlist.txt: 12822195310 bytes (81.69%) [snip] Dictionary cache built: Filename..: really-big-wordlist.txt Passwords.: 1212356398 Bytes.....: 15696118781 Keyspace..: 1196843344 [s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => Session..........: hashcat Status...........: Exhausted Hash.Type........: MD5 Hash.Target......: 38f63c3a621ad108457843529feec46a Time.Started.....: Sun Mar 26 06:38:05 2017 (1 min, 6 secs) Time.Estimated...: Sun Mar 26 06:39:11 2017 (0 secs) [snip] Started: Sun Mar 26 06:34:53 2017 (epoch: 1490510093) Stopped: Sun Mar 26 06:39:14 2017 (epoch: 1490510354)

Dictionary caching: 143s (54.79% - 2 mins, 23 secs)
Other setup: 52s (19.92% - 52 secs)
Total setup: 195s (74.71% - 3 mins, 15 secs)
Guessing: 66s (25.29% - 1 min, 6 secs )
Total time: 261s (4 mins, 21 secs)

Side note: the stats above are not part of hashcat's output, but they might be useful for others, so I've requested them as a feature.

Hey
i didnt understand what command have you tried

RE: How Calculate GPU Cracking Time - Dot - 03-28-2017

(03-27-2017, 01:58 PM)atom Wrote: You're looking for --speed-only

Hey
i tried to do that and got this
Speed Dev 65500 kH/s
that means that it tries 65550 passwords in a second from the word list?
isnt that slow?
im trying one hash using md5 with a0 attack
thanx

RE: How Calculate GPU Cracking Time - atom - 03-28-2017

Yes, that is very slow. If you use wordlists instead of brute-force you need to add an amplifier to get full speed on GPU.

RE: How Calculate GPU Cracking Time - Dot - 03-28-2017

How come with speed-only i get 65K results (image1)
and in the actual attack it goes down much less 4302 (image2)
so what is the right speed , meaning how many passwords from list my PC ties? [Image: ywUcIz2.png]

RE: How Calculate GPU Cracking Time - epixoip - 03-28-2017

Speed was lower because you cracked the password immediately, didn't get a chance to do any work. Moreover, as was already mentioned, you need to add an amplifier to gain any acceleration.

RE: How Calculate GPU Cracking Time - Dot - 03-28-2017

(03-28-2017, 04:32 PM)epixoip Wrote: Speed was lower because you cracked the password immediately, didn't get a chance to do any work. Moreover, as was already mentioned, you need to add an amplifier to gain any acceleration.

What is that mean amplifier?
also am im doing the right command to check my PC to see how many passwords he can try in a word list?
im using

Code:
hashcat64 -m0 "my hash" wordlist.txt --speed-only

or should i use something else

RE: How Calculate GPU Cracking Time - ytbe.use3 - 04-19-2017

(03-28-2017, 05:20 PM)Dot Wrote:
(03-28-2017, 04:32 PM)epixoip Wrote: Speed was lower because you cracked the password immediately, didn't get a chance to do any work. Moreover, as was already mentioned, you need to add an amplifier to gain any acceleration.
What is that mean amplifier?
also am im doing the right command to check my PC to see how many passwords he can try in a word list?
im using
Code:
hashcat64 -m0 "my hash" wordlist.txt --speed-only
or should i use something else

You said 65550 passwords in a second? Isn't it 65550* 1000 passwords in a second? (65500 kH/s)