mode 10500 dictionary attack fails
#11
I see the same behavior on another machine too (printout below), but frankly have no idea how to follow the advice "don't use OpenCL on Intel GPU". How do I avoid it?  

OpenCL API (OpenCL 2.1 ) - Platform #1 [Intel(R) Corporation]

=============================================================
* Device #1: Intel(R) HD Graphics 630, 1568/3212 MB (1023 MB allocatable), 23MCU
* Device #2: Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz, skipped

Also unclear is why would a buggy processor/API garble mode 10500 specifically (10 other modes I tested work fine).

Thanks a lot for your help!
Reply
#12
(01-25-2022, 05:42 PM)victorPV Wrote: I see the same behavior on another machine too (printout below), but frankly have no idea how to follow the advice "don't use OpenCL on Intel GPU". How do I avoid it?  

OpenCL API (OpenCL 2.1 ) - Platform #1 [Intel(R) Corporation]

=============================================================
* Device #1: Intel(R) HD Graphics 630, 1568/3212 MB (1023 MB allocatable), 23MCU
* Device #2: Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz, skipped

Also unclear is why would a buggy processor/API garble mode 10500 specifically (10 other modes I tested work fine).

Thanks a lot for your help!

well on this machine you could use 
Code:
-D 1 -d 2
to tell hashcat to just use the cpu instead of the default (gpu) and see if this fixes this misbehavior
Reply