This is another episode of the great AMD OpenCL runtime! I've just tested it locally with my NV GTX1080 and AMD RX480 with the same hashcat version (v3.30-157):
NV:
AMD
And just to verify it's not some code related problem, I've tested with Intel as well and it worked:
The problem with AMD (and NV, too) is that they don't care much about OpenCL as this is a nieche product that is not used by many customer. If we report bugs they will stay open forever, that's why we stopped reporting them. We can try to find a workaround for the problem, usually for the price of the performance drop, but finding such a workaround isn't guaranteed, too.
NV:
Quote:$RAR3$*0*b14426c0cf7c919a*e2efc1a653fae0b5999818f79f1ff014:123aA
Session..........: hashcat
Status...........: Cracked
Hash.Type........: RAR3-hp
AMD
Quote:Session..........: hashcat
Status...........: Exhausted
Hash.Type........: RAR3-hp
And just to verify it's not some code related problem, I've tested with Intel as well and it worked:
Quote:$RAR3$*0*b14426c0cf7c919a*e2efc1a653fae0b5999818f79f1ff014:123aA
Session..........: hashcat
Status...........: Cracked
Hash.Type........: RAR3-hp
The problem with AMD (and NV, too) is that they don't care much about OpenCL as this is a nieche product that is not used by many customer. If we report bugs they will stay open forever, that's why we stopped reporting them. We can try to find a workaround for the problem, usually for the price of the performance drop, but finding such a workaround isn't guaranteed, too.