Dissable or speedup autotune

[rodrigo.Brasil]

Autotune is not a problem in 95% of the usage.

But, when I try it with Mask Attack and get the mask from Extreme Breach Masks (a big list of mask for every size) and yet order the mask from faster to slower, I have a problem.

Like, for 9 digits, there is about 229k lines of mask. From every line it NEED to run the autotune. In this way, for the firsts nk lines, the time running the autotune is BIGGER than the time cracking it. When every line takes about 10 minutes, this will  not be problem.

So, why not hashcat just run the autotune once?  Why do it need to do for every entry in the mask attack? How can I dissable it or use the values it gets?

[royce]

I feel your pain. I wish there was an "--autotune-classic" or similar that would revert to the old method.

Today, the only way to disable autotuning is to manually add your own tuning. On the command line, this is done with -n/--kernel-accel and -u/--kernel-loops. If you do a run, and watch for the accel/loop values that are calculated by autotuning, you can just steal those values and use them and they won't suck.

Side note: if each mask only takes a few seconds to run and you're doing 229k of them, you can probably combine quite a few of them into larger masks.

[rodrigo.Brasil]

Today, the only way to disable autotuning is to manually add your own tuning. On the command line, this is done with -n/--kernel-accel and -u/--kernel-loops. If you do a run, and watch for the accel/loop values that are calculated by autotuning, you can just steal those values and use them and they won't suck.

The autotune just set this two values?  This is the same for every hash type and GPU? In other words, for the same hash and GPU, for every type of attack I try, the value will be the same? So, can I safety use it "hardcoded"?

Side note: if each mask only takes a few seconds to run and you're doing 229k of them, you can probably combine quite a few of them into larger masks.

Lol, this was just my first test. And yes, even without autotune, there is the time to start-stop every line. I will need to code a logic to make this more fast

[buka]

revert to the old method.

When did that change happen?

[royce]

The autotune just set this two values?  This is the same for every hash type and GPU? In other words, for the same hash and GPU, for every type of attack I try, the value will be the same? So, can I safety use it "hardcoded"?

Well, the tuning might be pretty different for different kinds of attacks. So you might want to run it and get the autotuned values for attacks of non-trivial run time.

[royce]

revert to the old method.

When did that change happen?

Some time between 6.2.3 and 6.2.4 IIRC?