Anyway to benchmark with specific parameters?
#9
(03-10-2017, 11:52 AM)atom Wrote: It's not hashcats fault, because the memory allocatable is limited by the OpenCL runtime. We've reported this to nvidia, here's a writeup: https://devtalk.nvidia.com/default/topic/992502

So then why doesn't hashcat use cuda to get around this weirdness? I read the thread and it's supposed to be a single allocation maximum, I can't seem to do any realistic values for scrypt on the gpu as it wants me to go up to 6 for the --scrypt parameter thing.

The binaries provided are opencl only from what I saw when I downloaded it, to get cuda I'd have to find some really old version of hashcat I guess then right?


Messages In This Thread
RE: Anyway to benchmark with specific parameters? - by 133794m3r - 03-10-2017, 05:10 PM