Litecoin wallet: Not cracking password (even known).
#1
Hi there.

It's been four weeks from now when I started with my forgotten wallet password recovery. Until yesterday I had a plan to wrote something with questions about encoding, but on the way to eliminate everything else, I discovered that new test-wallet can't be cracked even without any local character or any special character.

Is there some known issues with cracking Litecoin/Bitcoin wallet hashes? Any issues with wallet versions, Hashcat versions or something?

These are my steps:

0. Radeon HD5870 (yep, it's not too much, but maximum keyspace for me is about 3000)

0. Litecoin Core v0.14.2 (64-bit)

1. wallet.dat is copied to another machine on Linux.

2. There I get hash by bitcoin2john.py (hash looks OK).

3. Making files: .hash .dict (left and right), cracked.txt

4. Run:
Code:
hashcat64.exe -m 11300 wallet.hash -a 1 d1.dict d2.dict -o cracked.txt --self-test-disable -w 3 --status

5. Every reasonable encoding was tested (also inside .cmd file by adding "chcp"): UTF-8, UTF-8(noBOM), UTF-7, ANSI, ISO-8859-2, "Windows default". Possible special characters in my password: Polish letter "ł/Ł" and  tilde key "`".

6. Every time exhausted! Even when I'll set on new wallet four-characters password and run 
Code:
-m 11300 wallet.hash -a 3 pas?l

Any suggestions at this moment?
Or what can I add here to show more specific information?

I will be appreciate.

Best Regards.
syd
Reply
#2
>--self-test-disable

Let me guess. Hashcat said "self test failed" because your drivers are screwed up and instead of listening to the warning, you tried to suppress the warning and ignored it. If the self test failed, it will not be able to crack real hashes.
Reply
#3
(01-16-2018, 07:42 PM)Chick3nman Wrote: >--self-test-disable

Let me guess. Hashcat said "self test failed" because your drivers are screwed up and instead of listening to the warning, you tried to suppress the warning and ignored it. If the self test failed, it will not be able to crack real hashes.

I've tried few versions of drivers. At ones it didn't start another hangs on self-test. I would never have thought that if Hashcat starts with doing his job, that something can be wrong. Also about ignoring a self-test: this graphic card was a miner few years ago (BTC & LTC), so I thought that reason of not passing self-test is connected with weak condition of _some_ electronic components on board, which are not in all needed. With self-test it hangs on:
Code:
Initialized device kernels and memory...

But I still want to believe that hardware is not the reason and is about a wrong driver. So my question is about well working version of driver that You guys tested on Hashcat with ATI GPU (HD 5870 in my case)?
I know for sure, that beta (from v.16) doesn't works to me. Despite Win10Pro, the rest I'm putting as attachment to this post.

Thanks a lot for answering me!


Attached Files
.png   ati.PNG (Size: 22.89 KB / Downloads: 4)
Reply
#4
If you have a new CPU you could always use that if there is only 3000 possibilities. Otherwise, maybe take a look at just using the example hash to see if it fails as well.

Example Hash: 
$bitcoin$96$d011a1b6a8d675b7a36d0cd2efaca32a9f8dc1d57d6d01a58399ea04e703e8bbb44899039326f7a00f171a7bbc854a54$16$1563277210780230$158555$96$628835426818227243334570448571536352510740823233055715845322741625407685873076027233865346542174$66$625882875480513751851333441623702852811440775888122046360561760525

./hashcat64  -m 11300 -a 3 -w 4 bitcoin.txt hash?l?l?l

Otherwise, I would blame the old GPU with Incompatible drivers. Time to upgrade sir, or borrow someones hardware.
Reply