Quote from: HCP on November 30, 2017, 09:29:42 AM

And that is a MultiBit classic .key file?

Does the script generate a "parsed_wallet.txt" file? Does that file have some "encryption" information at the end like the salt and iterations and encryption type?

Hey, thank you for replying!

It's a Multibit classic .key file and I don't see a "parsed_wallet.txt" key. There's no information either.

Running:

Code:

openssl enc -d -aes-256-cbc -p -md md5 -a -in multibit.key -out newtest.txt

Gives me:

Code:

salt=2160B0AD6A6A5181
key=B0C5233E10A1227719077F3D5195ED45A5ABDEA796286F46120F2F86EF271251
iv =78A8C8A78F60194F0D44751683E1EC6A

But a file that again is jibberish.

ANOTHER EDIT:

If I run:

Code:

openssl enc -d -p -aes-256-cbc -a -in multibit.key -out test5.txt

Like it says to here: https://github.com/Multibit-Legacy/multibit/wiki/Export-and-limited-import-of-private-keys

It gives me this:

Code:

salt=2160B0AD6A6A5181
key=5340CEB7D94A3FE9754832332D9F3956B17B296E548FBCC85C74D4B658F72329
iv =BD773CE174D69C8716DB6264CDECD550
bad decrypt
20756:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:crypto\evp\evp_enc.c:536:

Though, I'm pretty sure this is the correct password as it's the only one that doesn't get the password error when I tried to unlock in Multibit classic. Instead it gives me:

Code:

The private keys unlock failed. The error was "Could not understand address in import file".