How to recover old multibit wallets?

[hippoduck]

I have several multibit wallets from 2014, the last version was unable to open my wallet files. My files consist of 77 byte strings a-z A-Z with some + signs.

How do I get access to these?

[Bonjur]

Same how to do this?

[hippoduck]

EDIT:

I removed my comment because it is wrong. The key is actually 76 characters long, and still appears to be a multibit encrypted wallet key. I'm looking for the solution still and will post here.

[hippoduck]

I found a comment on bitcointalk forum which others said worked successfully.

https://bitcointalk.org/index.php?topic=5304446.msg55964982#msg55964982

I'll quote it below in case it is removed later.

If you know the password... you can decrypt the .key files using openssl... the trick is that they changed a setting in openssl a few years back, and there is an extra commandline argument that you may need to include.

The explanation of the .key file format is here: https://github.com/Multibit-Legacy/multibit/wiki/Export%20and%20limited%20import%20of%20private%20keys

The recommended command line usually doesn't work:

openssl enc -d -p -aes-256-cbc -a -in <encrypted.key file> -out <plaintext file>

and you'll get something like the following "bad decrypt" error, even if the password is 100% correct!!?! Shocked: ...

bad decrypt
139987437556160:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:../crypto/evp/evp_enc.c:537:

But, by adding "-md md5" to the commandline, it should work as intended:

openssl enc -d -p -aes-256-cbc -md md5 -a -in <encrypted.key file> -out <plaintext file>

If you need/want to practise using openssl on .key files... so you know that it's working OK... you can use this .key file I just created in multibit 0.5.19: https://keybase.pub/hcp/cwoern.key As you can see, the contents of this .key file is similar to the one you posted earlier:

U2FsdGVkX18LSYm98B5HRgLWHgx35xMcsSpjjtdC9XG6iEYh9OC+vfyQA1fNmjEKs64cm/bntH7g /AMeb5NNSEe9hzYAgp/DRvOR+GX9E95pGcl4Gb2AHGMyUfAww7uV

The password (when prompted by openssl) is: abc123

The unencrypted file contents should be:

L2pUS76P4M1mPN98CRdHb64p2fVLzQuWQ44XadnsCospkiPjpweb 2020-11-29T16:15:26Z

NOTE: OpenSSL isn't included in Windows by default... but there are links to various binary downloads here: https://wiki.openssl.org/index.php/Binaries

I have personally downloaded/used the OpenSSL 1.1.1i 64bit binary from the "curl for win" page: https://curl.se/windows/ (source: https://github.com/curl/curl-for-win#binary-package-downloads) and successfully tested it with the cwoern.key and password from above.

[hippoduck]

Thank you but no thank you 😂

On Sat, 5 Feb 2022 at 15:46, password recovery @.***> wrote:

@joeyc002 https://github.com/joeyc002 I can recover your wallet if you still have this problem contact me at : @.***

— Reply to this email directly, view it on GitHub https://github.com/Multibit-Legacy/multibit/issues/811#issuecomment-1030647575, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJLSRKA4AGL73WEZA6LDSPTUZVA5PANCNFSM4ZJM4ZGQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

[doge2021]

you can reach www.btc2doge.com if you still have not recovered your multibit wallets