nOOb help
#11
So,
I did check the .potfile and it only has one cracked hash that was from a test I did right after I started working on hashcat. Also I didn't realize that a dictionary attack would require an exact word match, so it makes sense now that it didn't/probably won't ever work.

I then tried this mask attack:
hashcat64 -a 3 -m 7100 -o D:\HashcatCL\cracked.txt D:\HashcatCL\hashes\<hashfile>.txt ?1?1?1?1?1?1 -1 ?u?l?d

and when it ran and I checked the status it said estimated time (1 year, 321 days) for only 6 keyspaces. Yikes! So I quit the hashcat session.

I'm running a Radeon RX 460 4GB (I assume this is probably an embarrassing GPU)

The last line of the status check says:
Hardware.Mon.#1: Util: 69% Core: 1212MHz Mem:1750MHz Bus:8

Any ideas on what else I should do or try? I believe the target device password is probably more than 6 keyspaces anyway, which would probably make an exponentially longer hashcat estimated runtime. Am I not using my computer resources properly? Should I try a different attack?

Thx for the thoughts.
Reply


Messages In This Thread
nOOb help - by mh1 - 01-04-2019, 01:19 AM
RE: nOOb help - by philsmd - 01-04-2019, 11:09 AM
RE: nOOb help - by mh1 - 01-04-2019, 01:08 PM
RE: nOOb help - by Banaanhangwagen - 01-04-2019, 04:34 PM
RE: nOOb help - by mh1 - 01-06-2019, 12:17 AM
RE: nOOb help - by Banaanhangwagen - 01-07-2019, 12:32 PM
RE: nOOb help - by mh1 - 01-20-2019, 01:37 AM
RE: nOOb help - by philsmd - 01-20-2019, 10:03 AM
RE: nOOb help - by mh1 - 01-21-2019, 12:49 AM
RE: nOOb help - by Jefferson - 01-21-2019, 01:12 PM
RE: nOOb help - by mh1 - 01-22-2019, 10:28 PM
RE: nOOb help - by undeath - 01-23-2019, 12:20 PM
RE: nOOb help - by mh1 - 01-26-2019, 11:53 PM