03-25-2021, 01:47 PM
(This post was last modified: 03-26-2021, 01:28 AM by rsberzerker.
Edit Reason: Posted solution
)
Update: Solution below
I have a large list of NTLM hashes I got from my company's IT. I'm trying to crack them mostly for fun. I'm running hashcat 6.1.1 on Win10 using a Nvidia geoforce gtx 1060 (6GB). Judging by the lack of warnings, I finally got CUDA and the latest drivers installed correctly.
If I do a benchmark (hashcat.exe -b -m 1000), I get a cracking speed of about 22 BH/s. Looks good.
But when I run it against the my list, my speed becomes 2.2 MH/s. Right now I'm running a simple mask attack (?a x6) to eliminate some of the [should be] simple and easy hashes.
I remember reading that Nvidia is deliberately reducing the efficiency of its latest card by 50% when it is used to mine the crypto-currency Ethereum. It seems to be driver based. Could this be the reason my real hash rate is so low? I do see that my GPU utilization is near 0%.
The command line I use to start it is:
I did bump up the bitmap-max because when I used a lower value, hashcat warned me about running out of bitmap space and increasing it would help, so I did some trial and error and this is the lowest value that didn't give me that warning. But increasing it didn't seem to help, other than getting rid of the warning.
What can I do to get a better rate?
Solution: I found that by adding a limit to --markov-threshold (-t 5), my hashrate for the above jumped to ~650MH/s, a huge improvement. My GPU utilization rate also climbed. If you plan to let the mask go to exhaustion, your hashrate will be even faster if you add --markov-disable . Mine almost doubled to about 1.2BH/s with this.
I have a large list of NTLM hashes I got from my company's IT. I'm trying to crack them mostly for fun. I'm running hashcat 6.1.1 on Win10 using a Nvidia geoforce gtx 1060 (6GB). Judging by the lack of warnings, I finally got CUDA and the latest drivers installed correctly.
If I do a benchmark (hashcat.exe -b -m 1000), I get a cracking speed of about 22 BH/s. Looks good.
But when I run it against the my list, my speed becomes 2.2 MH/s. Right now I'm running a simple mask attack (?a x6) to eliminate some of the [should be] simple and easy hashes.
I remember reading that Nvidia is deliberately reducing the efficiency of its latest card by 50% when it is used to mine the crypto-currency Ethereum. It seems to be driver based. Could this be the reason my real hash rate is so low? I do see that my GPU utilization is near 0%.
The command line I use to start it is:
Quote:%hashcat% -m %hashtype% -a 3 --remove -O -o %outfile% --outfile-format=2 --status --bitmap-max=28 --session=rsmask %hashfile% "<path to mask file>rsmask.hcmask"
I did bump up the bitmap-max because when I used a lower value, hashcat warned me about running out of bitmap space and increasing it would help, so I did some trial and error and this is the lowest value that didn't give me that warning. But increasing it didn't seem to help, other than getting rid of the warning.
What can I do to get a better rate?
Solution: I found that by adding a limit to --markov-threshold (-t 5), my hashrate for the above jumped to ~650MH/s, a huge improvement. My GPU utilization rate also climbed. If you plan to let the mask go to exhaustion, your hashrate will be even faster if you add --markov-disable . Mine almost doubled to about 1.2BH/s with this.