bcrypt $2*$, Blowfish (Unix) slow speed
#1
Hi all,


Can someone tell me if  this is slow speed for a 8GB ASUS ROG STRIX GEFORCE GTX 1080 card ?
Session..........: 2018-09-11
Status...........: Running
Hash.Type........: bcrypt $2*$, Blowfish (Unix)
Hash.Target......: C:\Users\Kevo\AppData\Local\Temp\tmp2FAA.tmp
Time.Started.....: Tue Sep 11 19:22:14 2018 (29 mins, 5 secs)
Time.Estimated...: Sun Sep 16 06:46:55 2018 (4 days, 10 hours)
Guess.Base.......: File (C:\Program Files\HashcatGUI_1.00r3\hashcat-4.1.0\rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:      519 H/s (38.72ms) @ Accel:16 Loops:8 Thr:8 Vec:1
Recovered........: 3/17 (17.65%) Digests, 3/17 (17.65%) Salts
Progress.........: 1052160/243854528 (0.43%)
Rejected.........: 0/1052160 (0.00%)
Restore.Point....: 61440/14344384 (0.43%)
 
When I run a bench mark the results is much higher. Is it slow because I am running a dictionary attack?
Hashmode: 3200 - bcrypt $2*$, Blowfish (Unix) (Iterations: 32)

Speed.Dev.#1.....:    16266 H/s (38.28ms) @ Accel:16 Loops:8 Thr:8 Vec:1

Thanks for any info Kev
#2
What value is in the "cost" field of your hash? (the second $-separated field, two digits wide)?

Based on the speed you're getting, I'm guessing that it's probably cost 10? If so, that speed is normal for a 1080.
~
#3
(09-11-2018, 10:35 PM)royce Wrote: What value is in the "cost" field of your hash? (the second $-separated field, two digits wide)?

Based on the speed you're getting, I'm guessing that it's probably cost 10? If so, that speed is normal for a 1080.
Hello Royce,

Thank you for getting back to me .  This is the example I am using for practice
$2y$10$[redacted -royce]  . Why is this so slow then ? 

Cheers Kev
#4
(Unless you also post the plaintext, please don't post hashes.)

Your performance is quite normal for cost 10 on a 1080.
~
#5
(09-11-2018, 10:50 PM)royce Wrote: (Unless you also post the plaintext, please don't post hashes.)

Your performance is quite normal for cost 10 on a 1080.
 Sorry about that . And thanks again for getting back to me. I thought my new card had broke down.

Cheers Kev