trouble with all Litecoin wallets

[AndyML]

Greetings all.

I have an old Litecoin wallet (with very little in it) - I wanted to try to crack it as an exercise. First I tried patterns and masks that SHOULD have worked, but didn't. Eventually, in desperation, I switched to using a Dictionary that ONLY has the known correct password in it, and I still can't get hashcat to win with it.

I've made sure the hash is in the right format (from https://hashcat.net/wiki/doku.php?id=example_hashes) but hashcat fails to recognize the password. 

NOTE: I've used the same hash with btcrecovery.py and JohnTheRipper with success, so I believe the hash is valid. Here is the output of what I'm trying.

Code:

root@hostname:~/hashcat-4.0.1# ./hashcat64.bin -a 0 -m 11300 wallet.test.hash word hashcat (v4.0.1) starting... OpenCL Platform #1: Advanced Micro Devices, Inc. ================================================ * Device #1: Ellesmere, 3258/4082 MB allocatable, 32MCU * Device #2: Ellesmere, 3258/4082 MB allocatable, 32MCU Hashes: 1 digests; 1 unique digests, 1 unique salts Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates Rules: 1 Applicable optimizers: * Zero-Byte * Single-Hash * Single-Salt * Slow-Hash-SIMD-LOOP Password length minimum: 0 Password length maximum: 256 Watchdog: Temperature abort trigger set to 90c Watchdog: Temperature retain trigger set to 75c Initialized device kernels and memory...* Device #1: ATTENTION! OpenCL kernel self-test failed. Your device driver installation is probably broken. See also: https://hashcat.net/faq/wrongdriver * Device #2: ATTENTION! OpenCL kernel self-test failed. Your device driver installation is probably broken. See also: https://hashcat.net/faq/wrongdriver Dictionary cache hit: * Filename..: word * Passwords.: 1 * Bytes.....: 10 * Keyspace..: 1 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.           Session..........: hashcat                                 Status...........: Exhausted Hash.Type........: Bitcoin/Litecoin wallet.dat Hash.Target......: $bitcoin$96$8f5eeae78eccfd47e5somehashdetailsd25fe7e4...0d6b78 Time.Started.....: Thu Jan 11 12:49:48 2018 (6 secs) Time.Estimated...: Thu Jan 11 12:49:54 2018 (0 secs) Guess.Base.......: File (word) Guess.Queue......: 1/1 (100.00%) Speed.Dev.#1.....:        0 H/s (1.49ms) Speed.Dev.#2.....:        0 H/s (0.00ms) Speed.Dev.#*.....:        0 H/s Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts Progress.........: 1/1 (100.00%) Rejected.........: 0/1 (0.00%) Restore.Point....: 0/1 (0.00%) Candidates.#1....: $ACTUALPASSWORD -> $ACTUALPASSWORD Candidates.#2....: [Copying] HWMon.Dev.#1.....: Temp: 34c Fan: 44% Core: 588MHz Mem: 300MHz Bus:8 HWMon.Dev.#2.....: Temp: 43c Fan: 30% Core: 300MHz Mem:1750MHz Bus:8 Started: Thu Jan 11 12:48:38 2018 Stopped: Thu Jan 11 12:49:55 2018

Can anyone point me in the right direction? I'm stymied. Thanks!

[Chick3nman]

Hashcat literally tells you why it's not working in the output.

Code:

* Device #1: ATTENTION! OpenCL kernel self-test failed. Your device driver installation is probably broken. See also: https://hashcat.net/faq/wrongdriver * Device #2: ATTENTION! OpenCL kernel self-test failed. Your device driver installation is probably broken. See also: https://hashcat.net/faq/wrongdriver

If the self test fails, theres no expectation that the password will be properly found, as the test built into hashcat failed to crack properly. It's POSSIBLE to find a password after a kernel self test fails, but not expected. You will need to remedy that first.

[AndyML]

ha! I just figured that, since it bothered to go through all the calculations anyway, that it was actually testing them against the hash.

I'll work on it - thank you Chick3nman.