+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Error in Hashcat 3.10+532 (/thread-6001.html)
Error in Hashcat 3.10+532 - 5k33tz - 11-01-2016
Curious if anyone has been experiencing the "Salt-length exception" error while trying to crack sha256($pass.$salt) in the new hashcat beta?
For example, I can pass any length salt into hashcat v3.10, and it'll crack just fine, but while trying to pass the same salt length to the new hashcat beta, I get the exception error. I've tested the beta with salts of 8 characters and it works, but that's the only length it'll accept.
Is this just an issue with the beta, or will this be a permanent change in future releases?
v3.10:
root@<redacted>:/opt/programs/hashcat-3.10# ./hashcat64.bin -a 3 -1 ?l -m 1410 --hex-salt "64124e8740ea92838dcff1b7b2cf231264ae09eb2cf7c788e2a9f9b94abd8d51:856430BF8732" ?1?1?1?1?1?1?1
hashcat (v3.10) starting...
OpenCL Platform #1: NVIDIA Corporation
======================================
- Device #1: GeForce GTX TITAN X, 3071/12287 MB allocatable, 24MCU
- Device #2: GeForce GTX TITAN X, 3071/12287 MB allocatable, 24MCU
- Device #3: GeForce GTX TITAN X, 3071/12287 MB allocatable, 24MCU
- Device #4: GeForce GTX TITAN X, 3071/12287 MB allocatable, 24MCU
WARNING: Failed loading the X11 library: libX11.so: cannot open shared object file: No such file or directory
Please install libx11-dev package.
Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Early-Skip
* Not-Iterated
* Appended-Salt
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c
WARNING: Failed to set initial fan speed for device #1
WARNING: Failed to set initial fan speed for device #2
WARNING: Failed to set initial fan speed for device #3
WARNING: Failed to set initial fan speed for device #4
ATTENTION!
The wordlist or mask you are using is too small.
Therefore, hashcat is unable to utilize the full parallelization power of your device(s).
The cracking speed will drop.
Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_to_create_more_work_for_full_speed
INFO: approaching final keyspace, workload adjusted
64124e8740ea92838dcff1b7b2cf231264ae09eb2cf7c788e2a9f9b94abd8d51:856430bf8732:hashcat
Session.Name...: hashcat
Status.........: Cracked
Input.Mode.....: Mask (?1?1?1?1?1?1?1) [7]
Custom.Chars...: -1 ?l, -2 Undefined, -3 Undefined, -4 Undefined
Hash.Target....: 64124e8740ea92838dcff1b7b2cf231264ae09eb2...
Hash.Type......: sha256($pass.$salt)
Time.Started...: 0 secs
Speed.Dev.#1...: 1774.7 MH/s (2.81ms)
Speed.Dev.#2...: 1810.3 MH/s (3.25ms)
Speed.Dev.#3...: 1752.3 MH/s (2.74ms)
Speed.Dev.#4...: 1762.0 MH/s (2.73ms)
Speed.Dev.#*...: 7099.3 MH/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 634282688/8031810176 (7.90%)
Rejected.......: 0/634282688 (0.00%)
Restore.Point..: 0/456976 (0.00%)
Started: Tue Nov 1 12:43:34 2016
Stopped: Tue Nov 1 12:43:41 2016
beta:
root@<redacted>:/opt/programs/hashcat-3.10-beta# ./hashcat64.bin -a 3 -1 ?l -m 1410 --hex-salt "64124e8740ea92838dcff1b7b2cf231264ae09eb2cf7c788e2a9f9b94abd8d51:856430BF8732" ?1?1?1?1?1?1?1
hashcat (v3.10-620-gbd12a1e) starting...
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX TITAN X, 2047/12287 MB allocatable, 24MCU
* Device #2: GeForce GTX TITAN X, 2047/12287 MB allocatable, 24MCU
* Device #3: GeForce GTX TITAN X, 2047/12287 MB allocatable, 24MCU
* Device #4: GeForce GTX TITAN X, 2047/12287 MB allocatable, 24MCU
Hash '64124e8740ea92838dcff1b7b2cf231264ae09eb2cf7c788e2a9f9b94abd8d51:856430BF8732': Salt-length exception
No hashes loaded
Started: Tue Nov 1 12:52:24 2016
Stopped: Tue Nov 1 12:52:24 2016
RE: Error in Hashcat 3.10+532 - atom - 11-03-2016
This looks like a bug, thanks for report
RE: Error in Hashcat 3.10+532 - atom - 11-03-2016
Beta 623 is up and should fix the issue.
RE: Error in Hashcat 3.10+532 - 5k33tz - 11-03-2016
(11-03-2016, 12:42 AM)atom Wrote: Beta 623 is up and should fix the issue.
Thanks for the quick response. This fixed the issue.