Having some weird issues with cudahashcat.
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~# cudahashcat -m 0 -a 3 ./Desktop/hashes.hash ?d?d/?d?d/2013
I'm getting this exception:
WARNING: Hash './Desktop/hashes.hash': Line-length exception
ERROR: No hashes loaded
the file hashes.hash has the following contents:
Code:
07XXXXXXXXC67644D3C2131E16D88B18
15XXXXXXXX1EC5750430808A62F9E9A9
59XXXXXXXX6D8952845097534955EEED
71XXXXXXXX90CE6955736DFB1810ACA9
8BXXXXXXXX9781431084F51D8A43FE0A
2cXXXXXXXX03331674024c2f91a5b967
19XXXXXXXXf8eea199b9ae2f2b0a2e28
5dXXXXXXXXcde85e3372ad4b23482207
28XXXXXXXXc05725430ca7690d5d1bc9
83XXXXXXXXeeb74a7b6e62609c3a216b
24XXXXXXXXe5d33df13ac76c65ab4c60
d9XXXXXXXX5323ca2d1957059dc72499
Hashcat executes fine if I just run:
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~# hashcat -m 0 -a 3 ./Desktop/hashes.hash ?d?d/?d?d/2013
Any ideas?
Seems that the file './Desktop/hashes.hash' does not exist. Maybe path incorrect.
From this line:
WARNING: Hash './Desktop/hashes.hash': Line-length exception
we see, that it is trying to parse that parameter as a hash (not as a file)... since the file './Desktop/hashes.hash' does not exist.
Please try to copy hashes.hash to the current directory and try w/ tab completion to make sure that file exists (or ls it)
No luck
(edit: so I don't break the forum rules, I've replaced some of the chars in the post. Actual hashes.hash is just a list of md5 sums)
Code:
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Desktop/hashcat-forum-help# ls -al
total 136660
drwxr-xr-x 2 root root 4096 May 9 12:07 .
drwxr-xr-x 7 root root 4096 May 9 12:06 ..
-rw-r--r-- 1 root root 397 May 9 12:07 hashes.hash
-rw-r--r-- 1 root root 139921497 May 9 02:28 rockyou.txt
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Desktop/hashcat-forum-help# cat hashes.hash
07XXXXXXXXC67644D3C2131E16D88B18
15XXXXXXXX1EC5750430808A62F9E9A9
59XXXXXXXX6D8952845097534955EEED
71XXXXXXXX90CE6955736DFB1810ACA9
8BXXXXXXXX9781431084F51D8A43FE0A
2cXXXXXXXX03331674024c2f91a5b967
19XXXXXXXXf8eea199b9ae2f2b0a2e28
5dXXXXXXXXcde85e3372ad4b23482207
28XXXXXXXXc05725430ca7690d5d1bc9
83XXXXXXXXeeb74a7b6e62609c3a216b
24XXXXXXXXe5d33df13ac76c65ab4c60
d9XXXXXXXX5323ca2d1957059dc72499
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Desktop/hashcat-forum-help# cudahashcat -m 0 -a 3 hashes.hash ?d?d/?d?d/2013
WARNING: Hash 'hashes.hash': Line-length exception
ERROR: No hashes loaded
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
For anyone coming across this with the same problem, philsmd is right. An absolute path is required on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) (Currently 1.0.6).
Code:
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Desktop/cudaHashcat-1.20# cudahashcat -m 0 -a 3 /root/Desktop/hashcat-forum-help/hashes.hash ?a?a?a?a?a?a
cudaHashcat v1.01 starting...
Hashes: 12 total, 1 unique salts, 12 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Salt
* Brute-Force
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: GeForce GTX 660 Ti, 2047MB, 980Mhz, 7MCU
Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
Device #1: Kernel ./kernels/4318/m0000_a3.sm_30.64.ptx
Device #1: Kernel ./kernels/4318/markov_le_v1.64.ptx
Device #1: Kernel ./kernels/4318/bzero.64.ptx
[s]tatus [p]ause [r]esume [b]ypass [q]uit => q
Is there any known way of getting v1.2 to run? I did check, and the latest version is currently incompatible:
Code:
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Desktop/cudaHashcat-1.20# ./cudaHashcat64.bin
./cudaHashcat64.bin: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./cudaHashcat64.bin)
./cudaHashcat64.bin: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by ./cudaHashcat64.bin)
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Desktop/cudaHashcat-1.20# cudahashcat -V
1.01
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Desktop/cudaHashcat-1.20#
AFAIK installing experimental lib6c (fix posed by some other forums) is a bad thing. I ask as I'm now having problems with overheating (tried setting --gpu-loops=1, still overheats) and I wonder if this has been fixed since 1.01.
Thanks for sorting out my first issue philsmd. Legend. Just stupidity on my part.
