Missing options to specify opencl related params (OpenCL unusable)

[anthraxx]

Hi, it would be nice if some OpenCL related options could be used for configuration.
The easiest way would be to simply allow passing custom john parameters to the executable at the Settings tab below the executable.
This way OpenCL related parameters could be manually added (f.e. device type).

OpenCL usage can currently be activated by selecting md5crypt-opencl in the Options Tab under Current hash format but this results in missing parameters:
Console Log:

[19:12:27] /usr/bin/john --format=md5crypt-opencl --session=/home/foobar/.john/sessions/07-05-16-19-12-27 /tmp/foobar
Error: --device must be numerical, or one of "all", "cpu", "gpu" and
"accelerator".

[shinnok]

Having the ability to pass extra command line parameters for any type of attack is a must, especially since one can already pass extra ENV vars via the Attack Options -> Other options section. That's where the extra command line params should go also, this issue has been assigned to milestone 2.3.

Thanks for the report!

[solardiz]

[19:12:27] /usr/bin/john --format=md5crypt-opencl --session=/home/foobar/.john/sessions/07-05-16-19-12-27 /tmp/foobar
Error: --device must be numerical, or one of "all", "cpu", "gpu" and "accelerator".

This output suggests that a --device option was in fact specified, but had a wrong argument to it. Why would that be? Puzzled.

--format=md5crypt-opencl should have worked on its own (without any --device option), picking the first OpenCL device in older jumbo and the expected-fastest OpenCL device in current bleeding-jumbo.