Since you use:
instead of
(i.e. - last command example - cudaHashcat64.bin is in current directory)
I assume that the The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) installation has some sort of wrapper and you need to specify an absolute path e.g. /home/root/hashes.hash (make sure that the file containing the hashes is there or copy it to that path).
The wrapper may "change" (the current directory) to a different path, therefore all relative urls like ./Desktop/... or ./hashes.hash are interpretate wrongly.
The fix is to:
1. either change to the location where the real binary is installed (you can search for it by sudo updatedb; locate cudaHashcat64.bin) and run the binary directly from that path (you may also need to copy the hashes.hash file etc)
2. use absolute paths starting w/ '/' e.g. '/home/root' or similar
Code:
cudahashcat ...instead of
Code:
./cudahashcat ...(i.e. - last command example - cudaHashcat64.bin is in current directory)
I assume that the The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) installation has some sort of wrapper and you need to specify an absolute path e.g. /home/root/hashes.hash (make sure that the file containing the hashes is there or copy it to that path).
The wrapper may "change" (the current directory) to a different path, therefore all relative urls like ./Desktop/... or ./hashes.hash are interpretate wrongly.
The fix is to:
1. either change to the location where the real binary is installed (you can search for it by sudo updatedb; locate cudaHashcat64.bin) and run the binary directly from that path (you may also need to copy the hashes.hash file etc)
2. use absolute paths starting w/ '/' e.g. '/home/root' or similar