Strange data in input of .cl program
#2
hmm, I didn't test it yet fully, but I normally don't use %s prints in kernel files.

I would rather print it in hex:
Code:
printf ("%08x %08x%08x%08x%08x %d\n", hash, w[0], w[1], w[2], w[3], pw_len);

In this case it could also be the problem with u32x vs u32 , but if you say it worked before, its' very unlikely the main problem.

how do you test it, are these the only parameters you use ?

I would recommend to use some command line options (also mentioned in the guide) like this:
Code:
-a 3 -n 1 -u 1 -T 1 --self-test-disable --backend-vector-width 1 --force hash.txt testmask

at least this way you restrict the kernel power and the amount of password candidates that are being tested (always better to start small and in a step-by-step approach when still developing the kernel).

Test it like this and if you still have some doubts, feel free to ask (and yeah, some devs here including me can also have a closer look at the source code if you still have problems with this new test).
Reply


Messages In This Thread
RE: Strange data in input of .cl program - by philsmd - 04-26-2021, 10:46 AM