Does anyone at all know what these 2 values in the YAML file could be used for?
I guess I am going to do a deep dive into the Multibit HD code itself to find out how it gets utilized, but if in the meantime anybody actually knows something about this.
I hope I can figure this out because my cut is about $20K worth of the BTC.
Topic: Multibit HD YAML Files with encryptedPassword and encryptedBackupKey (Read 93 times)
December 26, 2024, 06:56:03 PM
December 26, 2024, 01:23:49 PM
Test password variations; as you mentioned a possible issue with UTF-16, try removing or adding trailing spaces, test versions with and without uppercase letters, and if your password contains special characters, convert them to their ASCII forms
Perform brute force; extract the base64 data from the "encryptedPassword" and use a script to test various password combinations. If you're able to decrypt this block, then that's the correct password
You can also perform brute force directly on the ".wallet" file. Since you have "continuous backups" and ZIP backups, you have multiple snapshots to test — sometimes, an older file may not have the same corruption as a later version
That's all I know so far; I hope I can help you
Perform brute force; extract the base64 data from the "encryptedPassword" and use a script to test various password combinations. If you're able to decrypt this block, then that's the correct password
You can also perform brute force directly on the ".wallet" file. Since you have "continuous backups" and ZIP backups, you have multiple snapshots to test — sometimes, an older file may not have the same corruption as a later version
That's all I know so far; I hope I can help you
December 26, 2024, 12:53:09 PM
Yeah I have decoded it, but what is the use of it? Is this only a part of what is needed for decrypting the backup files?
December 26, 2024, 12:07:18 PM
== means base64 encoding
December 26, 2024, 09:38:53 AM
I have a Multibit HD wallet that has more than .5 BTC in it that needs recovering.
It is a pretty rough situation I am trying to workout for someone and is as follows.
The person was really good about keeping seed words up until this last time.
He then became affected by the error of knowing the password, but it doesn't unlock the wallet.
I have tried:
mbexport and forked version
decrypt_bitcoinj_seed-master
I have run many different token variations on the password in hopes that it gets a bite if just some of the characters were off (from what I read that bug related to how UTF 16 translated?).
What I do find interesting is that the old YAML files from the prior wallets (version 0.4.1) of Multibit HD only had some basic preferences settings (Show balance: true..etc). However, the YAML files for the 0.5.1 version of Multibit HD has 2 values show as:
encryptedPassword: 88 Characters with +, / and == at the end
encryptedBackupKey: 64 Characters with / and + but no = sign
My main question for the post is to find out where these would be useful as I do have the rolling and zip backup files as well.
It is a pretty rough situation I am trying to workout for someone and is as follows.
The person was really good about keeping seed words up until this last time.
He then became affected by the error of knowing the password, but it doesn't unlock the wallet.
I have tried:
mbexport and forked version
decrypt_bitcoinj_seed-master
I have run many different token variations on the password in hopes that it gets a bite if just some of the characters were off (from what I read that bug related to how UTF 16 translated?).
What I do find interesting is that the old YAML files from the prior wallets (version 0.4.1) of Multibit HD only had some basic preferences settings (Show balance: true..etc). However, the YAML files for the 0.5.1 version of Multibit HD has 2 values show as:
encryptedPassword: 88 Characters with +, / and == at the end
encryptedBackupKey: 64 Characters with / and + but no = sign
My main question for the post is to find out where these would be useful as I do have the rolling and zip backup files as well.
Jump to: