linker command failed/Final linking of kernel gpu_decompress failed.

[windowshopr]

I ran into this issue with hashcat earlier today, so I uninstalled and re-installed, same issue.

I'm trying to run this command:

Code:

sudo hashcat -m 22001 -a 3 WPA*01*9660cab2a78529b0db720296d1edf9d3*c089ab84f750*705a0f7a6835*5341534b54454c30304448*** ?u?u?u?u -d 1 -v --backend-ignore-cuda

-m tried 22000 and 22001 for the hash type
-a 3 for brute force
-d 1 for cpu
--backend-ignore-cuda as the error alludes to a gpu issue, which I don't have a GPU in this laptop.

I've updated my The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) Linux environment with update and upgrade before attempting the clean install of hashcat, same issue.

What does this error mean? Here is the full traceback:

Code:

OpenCL API (OpenCL 2.0 pocl 1.8  Linux, None+Asserts, RELOC, LLVM 9.0.1, SLEEF, DISTRO, POCL_DEBUG) - Platform #1 [The pocl project]
====================================================================================================================================
* Device #1: pthread-Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2761/5586 MB (1024 MB allocatable), 4MCU

OpenCL API (OpenCL 2.1 LINUX) - Platform #2 [Intel(R) Corporation]
==================================================================
* Device #2: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, skipped

Minimum password length supported by kernel: 64
Maximum password length supported by kernel: 64

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
* Slow-Hash-SIMD-LOOP

Watchdog: Temperature abort trigger set to 90c

Initializing backend runtime for device #1. Please be patient.../usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libm.so.6 when searching for /lib/x86_64-linux-gnu/libm.so.6
/usr/bin/ld: cannot find /lib/x86_64-linux-gnu/libm.so.6
/usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libm.so.6 when searching for /lib/x86_64-linux-gnu/libm.so.6
/usr/bin/ld: /lib/x86_64-linux-gnu/libmvec.so.1: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libmvec.so.1 when searching for /lib/x86_64-linux-gnu/libmvec.so.1
/usr/bin/ld: cannot find /lib/x86_64-linux-gnu/libmvec.so.1
/usr/bin/ld: /lib/x86_64-linux-gnu/libmvec.so.1: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libmvec.so.1 when searching for /lib/x86_64-linux-gnu/libmvec.so.1
error: linker command failed with exit code 1 (use -v to see invocation)
Final linking of kernel gpu_decompress failed.
zsh: IOT instruction  sudo hashcat -m 22001 -a 3  ?u?u?u?u -d 1 -v --backend-ignore-cuda

[slyexe]

Install the proper drivers, don't use POCL project. Use ROCM or official Intel Drivers.

Code:

sudo hashcat -m 22001 -a 3  ?u?u?u?u -d 1 -v --backend-ignore-cuda

This also makes no sense, you have no hash applied to your command. Use hashcat -h for proper parameter usage, using shell or terminal also can have issues using special characters so placing your hashes within a text file is best suitable to avoid conflictions within terminals.

[windowshopr]

Install the proper drivers, don't use POCL project. Use ROCM or official Intel Drivers.

Code:

sudo hashcat -m 22001 -a 3  ?u?u?u?u -d 1 -v --backend-ignore-cuda

This also makes no sense, you have no hash applied to your command.  Use hashcat -h for proper parameter usage, using shell or terminal also can have issues using special characters so placing your hashes within a text file is best suitable to avoid conflictions within terminals.

Thanks! I'll look into installing the proper drivers!

And that last part is just the output from the traceback. If you look at the command I entered further up, I DO provide a hash value, and have also tried supplying an actual .hccapx and .hc22000 file, same result. I'll try and document my steps for getting this working...

[windowshopr]

Ok, so far, nothing.

When I follow the installation steps for the latest release of OpenCL at their Github page, here:

https://github.com/intel/compute-runtime...3.24595.30

...I get a missing package issue about one of the dependencies as it doesn't seem to be included, so I first install a previous version:

wget https://github.com/intel/compute-runtime..._amd64.deb
wget https://github.com/intel/intel-graphics-..._amd64.deb
wget https://github.com/intel/intel-graphics-..._amd64.deb
wget https://github.com/intel/compute-runtime...amd64.ddeb
wget https://github.com/intel/compute-runtime..._amd64.deb
wget https://github.com/intel/compute-runtime...amd64.ddeb
wget https://github.com/intel/compute-runtime..._amd64.deb
sudo dpkg -i *.deb

...and try the crack again, same issue. Then I try to follow similar steps above for the latest version, same issue. So I'm going to try ROCM next I guess?

[windowshopr]

Ok after a long battle, I was finally able to install the Intel OpenCL library, even though it says Debian/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) is not supported.

HOWEVER, now I ran into this issue:

Minimum password length supported by kernel: 64
Skipping mask '?u?u?u?u' because it is smaller than the minimum password length.

Why is my minimum password length set so high? Can I change it? to say, 1????

[ZerBea]

hash mode 22000 is to recover a PSK (Pre Shared Key) which can be 8 ... 63 characters
hash mode 22001 is to verify a PMK (Plain Master Key) which is always 64 HEX characters.

Your mask (?u?u?u?u) is too short to recover a PSK

[windowshopr]

Oh I see, that number changes with the different hash types you choose, got it.

Don't get too hung up on that, it's just there for visual reference so I don't have to put ?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u for the mask lol

[Snoopy]

dont really sure about linux but on windows -d1 only works in conjunction with -D1, as hashcat defaults to type2, so the right options for using cpu is

-D1 -d1

example plain cpu setup:
hashcat -d1 -b -m0
No devices found/left

hashcat -D1 -d1 -b -m0
Speed.#1.........: 1240.5 MH/s