PoCL OpenCL cannot crack in mode 1800 - sha512crypt $6$, SHA512 (Unix)
Author: PSLLSPCreated Sep 7, 2026Updated Sep 8, 2026
I see that I should not report issues with PoCL OpenCL runtime. I report it anyway because when I run hashcat in mode 1000 (NTLM) or 7400 (sha256crypt) it works OK. When I try mode 1800 (sha512crypt) it fails. Good news is it detect that something is wrong with OpenCL...
$ cat /tmp/secret-test3.txt
test:$6$mAFvuV4VL/sO9/Vp$zW.mLIy6ae7Cpy4uozKmKNuAoqwTjIWznMfHLPp.eaqqPrZcuJz3yzi0NoR27AJXujNkxHqKjba9gKc23w/A80:19094:0:99999:7:::$ ~/Downloads/hashcat-7.1.2/hashcat.bin -a3 /tmp/secret-test3.txt ?l?l?l?l
hashcat (v7.1.2) starting in autodetect mode
* Device #2: Outdated PoCL OpenCL runtime detected!
You can use --force to override, but do not report related errors.
OpenCL API (OpenCL 3.0 ) - Platform #1 [Intel(R) Corporation]
=============================================================
* Device #01: Intel(R) UHD Graphics [0x9a78], 7879/15758 MB (2047 MB allocatable), 16MCU
OpenCL API (OpenCL 2.0 pocl 1.8 Linux, None+Asserts, RELOC, LLVM 11.1.0, SLEEF, DISTRO, POCL_DEBUG) - Platform #2 [The pocl project]
=====================================================================================================================================
* Device #02: pthread-11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz, skipped
Hash-mode was not specified with -m. Attempting to auto-detect hash mode.
The following mode was auto-detected as the only one matching your input hash:
1800 | sha512crypt $6$, SHA512 (Unix) | Operating System
NOTE: Auto-detect is best effort. The correct hash-mode is NOT guaranteed!
Do NOT report auto-detect issues unless you are certain of the hash type.
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Minimum salt length supported by kernel: 0
Maximum salt length supported by kernel: 256
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Optimizers applied:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Uses-64-Bit
* Register-Limit
ATTENTION! Pure (unoptimized) backend kernels selected.
Pure kernels can crack longer passwords, but drastically reduce performance.
If you want to switch to optimized kernels, append -O to your commandline.
See the above message to find out about the exact limits.
Watchdog: Temperature abort trigger set to 90c
Host memory allocated for this attack: 724 MB (6737 MB free)
clWaitForEvents(): CL_EXEC_STATUS_ERROR_FOR_EVENTS_IN_WAIT_LIST
clFinish(): CL_OUT_OF_RESOURCES
Aborting session due to kernel self-test failure.
You can use --self-test-disable to override, but do not report related errors.
Started: Tue Sep 8 00:20:24 2026
Stopped: Tue Sep 8 00:20:36 2026When I run hashcat with parameter --force it detects an issue and exits, that is good...
$ ~/Downloads/hashcat-7.1.2/hashcat.bin -a3 --force /tmp/secret-test3.txt ?l?l?l?l
hashcat (v7.1.2) starting in autodetect mode
You have enabled --force to bypass dangerous warnings and errors!
This can hide serious problems and should only be done when debugging.
Do not report hashcat issues encountered when using --force.
OpenCL API (OpenCL 3.0 ) - Platform #1 [Intel(R) Corporation]
=============================================================
* Device #01: Intel(R) UHD Graphics [0x9a78], 7879/15758 MB (2047 MB allocatable), 16MCU
OpenCL API (OpenCL 2.0 pocl 1.8 Linux, None+Asserts, RELOC, LLVM 11.1.0, SLEEF, DISTRO, POCL_DEBUG) - Platform #2 [The pocl project]
=====================================================================================================================================
* Device #02: pthread-11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz, skipped
Hash-mode was not specified with -m. Attempting to auto-detect hash mode.
The following mode was auto-detected as the only one matching your input hash:
1800 | sha512crypt $6$, SHA512 (Unix) | Operating System
NOTE: Auto-detect is best effort. The correct hash-mode is NOT guaranteed!
Do NOT report auto-detect issues unless you are certain of the hash type.
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Minimum salt length supported by kernel: 0
Maximum salt length supported by kernel: 256
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Optimizers applied:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Uses-64-Bit
* Register-Limit
ATTENTION! Pure (unoptimized) backend kernels selected.
Pure kernels can crack longer passwords, but drastically reduce performance.
If you want to switch to optimized kernels, append -O to your commandline.
See the above message to find out about the exact limits.
Watchdog: Temperature abort trigger set to 90c
Host memory allocated for this attack: 724 MB (6716 MB free)
clWaitForEvents(): CL_EXEC_STATUS_ERROR_FOR_EVENTS_IN_WAIT_LIST
clFinish(): CL_OUT_OF_RESOURCES
Aborting session due to kernel self-test failure.
You can use --self-test-disable to override, but do not report related errors.
Started: Tue Sep 8 00:29:58 2026
Stopped: Tue Sep 8 00:30:09 2026Source: hashcat/hashcat