Please note, this is a STATIC archive of website hashcat.net from 08 Oct 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.
hashcat Forum
5.1.0+1394 not processing LM hashes - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Developer (https://hashcat.net/forum/forum-39.html)
+--- Forum: Beta Tester (https://hashcat.net/forum/forum-31.html)
+--- Thread: 5.1.0+1394 not processing LM hashes (/thread-8610.html)



5.1.0+1394 not processing LM hashes - slawson - 08-28-2019

I'm notĀ for sure if I amĀ supposed to report bugs for beta versions, but it seems the latest beta will not load any LM hashes for processing.


RE: 5.1.0+1394 not processing LM hashes - undeath - 08-28-2019

cannot reproduce

Code:
./hashcat -m 3000 299bd128c1101fd6 -a3 hashca?l
hashcat (v5.1.0-1397-g7f4df9eb) starting...

* Device #2: CUDA SDK Toolkit installation NOT detected.
             CUDA SDK Toolkit installation required for proper device support and utilization
             Falling back to OpenCL Runtime

* Device #2: WARNING! Kernel exec timeout is not disabled.
             This may cause "CL_OUT_OF_RESOURCES" or related errors.
             To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL API (OpenCL 1.2 LINUX) - Platform #1 [Intel(R) Corporation]
==================================================================
* Device #1: AMD Ryzen 5 1600 Six-Core Processor, skipped

OpenCL API (OpenCL 1.2 CUDA 10.1.120) - Platform #2 [NVIDIA Corporation]
========================================================================
* Device #2: GeForce GTX 1060 6GB, 1519/6077 MB allocatable, 10MCU

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 7

Watchdog: Temperature abort trigger set to 90c

Host memory required for this attack: 239 MB

The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework

Approaching final keyspace - workload adjusted.  

299bd128c1101fd6:HASHCAT                        
                                                
Session..........: hashcat
Status...........: Cracked
Hash.Name........: LM
Hash.Target......: 299bd128c1101fd6
Time.Started.....: Wed Aug 28 18:17:26 2019 (0 secs)
Time.Estimated...: Wed Aug 28 18:17:26 2019 (0 secs)
Guess.Mask.......: hashca?l [7]
Guess.Queue......: 1/1 (100.00%)
Speed.#2.........:    62919 H/s (0.04ms) @ Accel:128 Loops:1024 Thr:64 Vec:1
Recovered........: 1/1 (100.00%) Digests
Progress.........: 26/26 (100.00%)
Rejected.........: 0/26 (0.00%)
Restore.Point....: 0/26 (0.00%)
Restore.Sub.#2...: Salt:0 Amplifier:0-1 Iteration:0-1024
Candidates.#2....: HASHCAN -> HASHCAQ
Hardware.Mon.#2..: Temp: 41c Fan: 31% Util:  9% Core:1657MHz Mem:3802MHz Bus:16

Started: Wed Aug 28 18:17:25 2019
Stopped: Wed Aug 28 18:17:28 2019