hashcat Forum
How to optimize attacking very large hashes - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html)
+--- Forum: General Help (https://hashcat.net/forum/forum-8.html)
+--- Thread: How to optimize attacking very large hashes (/thread-5517.html)

How to optimize attacking very large hashes - azren - 06-14-2016

Hi,

I'm trying to attack a very large hashes, few GB in size and manage to get it down now to a few hundreds MB. The problem is that it takes a long time to:
  • remove recovered hashes from the hash file (i'm using --remove)


Example:
doing -a 3 ?a?a?a?a?a?a attack completed fast on my 2 x GTX 1080, but to get back to command prompt will take a while
  • when loading, it takes a long time to compare hashes with pot file
Code:
Comparing hashes with potfile entries...

How can I optimize this and make it a lot faster.

Thank you.

Best regards,
Azren

RE: How to optimize attacking very large hashes - kiara - 06-14-2016

(06-14-2016, 08:08 AM)azren Wrote: Hi,

I'm trying to attack a very large hashes, few GB in size and manage to get it down now to a few hundreds MB. The problem is that it takes a long time to:
  • remove recovered hashes from the hash file (i'm using --remove)


Example:
doing -a 3 ?a?a?a?a?a?a attack completed fast on my 2 x GTX 1080, but to get back to command prompt will take a while
  • when loading, it takes a long time to compare hashes with pot file
Code:
Comparing hashes with potfile entries...

How can I optimize this and make it a lot faster.

Thank you.

Best regards,
Azren
from what i understand from what u are saying is, u are using --remove so each hash u recover his password is removed from the list, and what take time is to reading from the pot file, 
why not just to change the name of pot file so hashcat wont read from it.
u can also try to remove duplicate recover hashes

RE: How to optimize attacking very large hashes - epixoip - 06-14-2016

Don't use --remove, use --show and --left with -o /dev/null instead.

RE: How to optimize attacking very large hashes - azren - 06-15-2016

That helps. Saved me about 5 to 10 minutes per iteration. Thanks.

Best regards,
Azren