OpenCl kernel self-test failed when using any version later than v4.2.1 !!
#11
I appreciate why this change happened, but from a UX perspective, especially for users who are not developers or very busy and not tracking hashcat release notes, is there any way to at least detect the presence of the bug and explain in a little more detail, something like:

"OpenCL kernel self-test failed - probable AMD OpenCL bug (not hashcat)"

?
~
Reply
#12
There's not much to say in terms of error message. This error occurs if the self-test hash was not cracked but it should be cracked. That's all we know.
Reply
#13
(02-13-2019, 05:06 PM)atom Wrote: There's not much to say in terms of error message. This error occurs if the self-test hash was not cracked but it should be cracked. That's all we know.

If i use --force (cause of specific optimization), does it still self-test?
Reply
#14
During testing on test versions I use the driver (Win10-64Bit-Radeon-Software-Adrenalin-Edition-18.5.1-May23)
After version (hashcat-5.1.0 + 910) the mechanism broke.
[Image: a30594bd199f1103fc7680667709c3a6.jpg]

[Image: 162f28eb61033adca40a5747a145464e.jpg]
Reply
#15
So today (hashcat-5.1.0 + 1012) there are no changes in a good direction.

[Image: fb130775c1ed73be1547afe18582d1fe.jpg]
Reply