06-06-2018, 04:33 PM
Thanks for the quick response! When I remove --force, I get an error about my GPU, but I'm on a laptop and am ok with hashcat using my CPU to crunch through the 10,000 iterations needed for the password space.
I did try the --hex-salt (and --hex-charset) modifiers but didn't see any apparent change in the results.
It would help to narrow down the trouble if someone could run my command on their machine:
hashcat64.exe -m 10 e2c704ed395b06bf492d95fd4ad3a964:081cec9952979615 -a 3 ?d?d?d?d --force --hex-salt
(or the ./hashcat64.bin equivalent) and let me know if they're getting any errors or just the cracked pin 1234.
Here's the error I get if I remove --force:
* Device #1: Intel's OpenCL runtime (GPU only) is currently broken.
We are waiting for updated OpenCL drivers from Intel.
You can use --force to override, but do not report related errors.
* Device #3: Intel's OpenCL runtime (GPU only) is currently broken.
We are waiting for updated OpenCL drivers from Intel.
You can use --force to override, but do not report related errors.
No devices found/left.
Thanks,
I did try the --hex-salt (and --hex-charset) modifiers but didn't see any apparent change in the results.
It would help to narrow down the trouble if someone could run my command on their machine:
hashcat64.exe -m 10 e2c704ed395b06bf492d95fd4ad3a964:081cec9952979615 -a 3 ?d?d?d?d --force --hex-salt
(or the ./hashcat64.bin equivalent) and let me know if they're getting any errors or just the cracked pin 1234.
Here's the error I get if I remove --force:
* Device #1: Intel's OpenCL runtime (GPU only) is currently broken.
We are waiting for updated OpenCL drivers from Intel.
You can use --force to override, but do not report related errors.
* Device #3: Intel's OpenCL runtime (GPU only) is currently broken.
We are waiting for updated OpenCL drivers from Intel.
You can use --force to override, but do not report related errors.
No devices found/left.
Thanks,