yeah, very very good explanation @Mem5. your post is perfect because it explains what I forgot to mention above...
From my experience from the last couple of months/years, is that some people confuse the lower-case parameter with the correct upper-case parameter -D 1 (that stands for --opencl-device-types).
That means you need to use -D 1 (or -D 1,2) to even allow the CPU to run (if you have both CPUs AND GPUs)... if you only have CPUs, hashcat automatically allows CPUs too.
This implies that -D 1,2 or (-D 1 for only CPU) is needed to whitelist the CPUs, but the lowercase parameter (dash + lower case d) is something completely different, i.e. --backend-devices. The lower-case d allows you to select the different devices that are allowed to run (already whitelisted with -D). It should be very obvious now what the difference is between --opencl-device-types (-D) and --backend-devices (the "wrong" in your case, dash + lower case d).
Again, I saw a lot of users that just think it's "dash d that I need to use", without even checking the --help output and understanding that the command line parameter they use does something completely different.
That means, that instead of the dash+lowercase you currently use, you might want to test with and use:
or
instead.
From my experience from the last couple of months/years, is that some people confuse the lower-case parameter with the correct upper-case parameter -D 1 (that stands for --opencl-device-types).
That means you need to use -D 1 (or -D 1,2) to even allow the CPU to run (if you have both CPUs AND GPUs)... if you only have CPUs, hashcat automatically allows CPUs too.
This implies that -D 1,2 or (-D 1 for only CPU) is needed to whitelist the CPUs, but the lowercase parameter (dash + lower case d) is something completely different, i.e. --backend-devices. The lower-case d allows you to select the different devices that are allowed to run (already whitelisted with -D). It should be very obvious now what the difference is between --opencl-device-types (-D) and --backend-devices (the "wrong" in your case, dash + lower case d).
Again, I saw a lot of users that just think it's "dash d that I need to use", without even checking the --help output and understanding that the command line parameter they use does something completely different.
That means, that instead of the dash+lowercase you currently use, you might want to test with and use:
Code:
-D 1Code:
-D 1,2