Line-length

[wproctor]

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.