search

gurnec / btcrecover

An open source Bitcoin wallet password and seed recovery tool designed for the case where you already know most of your password/seed, but need assistance in trying different possible combinations.
GNU General Public License v2.0
1.29k stars 688 forks source link

Error message: "... not encrypted" #126

Open jnbordnrt opened 7 years ago

jnbordnrt commented 7 years ago

Hi,

Firstly, thank you for taking the initiative and spending your time working on this. If it helps my situation, I am DEFINITELY donating to your address. I'm very hopeful.

I have a situation come up during my upgrade to the new mSigna version 10.6 where it appears to have created addresses for unspent coins that are not showing up in my address list and hence, not showing accurately in the wallet balance. My thought is that, if I have my private key (something I'm hoping this will give me), then I can directly spend those coins on blockchain.info.

I know all my pass-phrases for my seed in mSigna but cannot seem to get the private key. But perhaps I am expecting something different from your intention. Is there a way to get the private key from the mnemonic? I have tried BIP32.org to no avail - probably because I don't know mSigna's derivation path.

I used the following command line with the result that it says my account is "not encrypted". Any idea what's going on? I have read most of the documentation (thanks for that btw) but didn't see this message.

One aside: The wallet account (one of three) I am trying to open is "JimMain 1" but I used "JimMain_1" in the command line which appears to work.

Jims-Air:btcrecover-master jim$ python btcrecover.py --wallet newmain.vault --msigna-keychain JimMain_1 --tokenlist tokens.txt Starting btcrecover 0.17.8 on Python 2.7.14 64-bit, 16-bit unicodes, 64-bit ints btcrecover.py: error: mSIGNA keychain 'JimMain 1' is not encrypted

gurnec commented 6 years ago

mSIGNA is a somewhat complicated wallet that's changed a lot over time... can you offer some additional details?

How many keychains do you have in your vault file? Do you have any problems exporting each keychain as a wordlist (right-click, "Export", "To wordlist")? If you try this, are you ever asked to unlock your keychain with a password?

How many accounts do you have? Are their policies (from the Policy column) all "1 of one-account-name", or something more complex?

If you look at the address lists of each account, does each address start with a "1" or a "3" (or a mix)?

Have you tried creating a new vault, importing your wordlists as new keychains (via the Keychains -> Import menu), and creating new accounts after that to see if your balance reappears?

jnbordnrt commented 6 years ago

Hi Christopher,

Thank you for the email. Can you read this? I’d rather talk privately about this for now due to sensitivity.

Thanks

Tristan

From: Christopher Gurnee notifications@github.com Reply-To: gurnec/btcrecover reply@reply.github.com Date: Friday, November 3, 2017 at 6:22 AM To: gurnec/btcrecover btcrecover@noreply.github.com Cc: Tristan Whitehead jnbordnrt@gmail.com, Author author@noreply.github.com Subject: Re: [gurnec/btcrecover] Error message: "... not encrypted" (#126)

mSIGNA is a somewhat complicated wallet that's changed a lot over time... can you offer some additional details?

How many keychains do you have in your vault file? Do you have any problems exporting each keychain as a wordlist (right-click, "Export", "To wordlist")? If you try this, are you ever asked to unlock your keychain with a password?

How many accounts do you have? Are their policies (from the Policy column) all "1 of one-account-name", or something more complex?

If you look at the address lists of each account, does each address start with a "1" or a "3" (or a mix)?

Have you tried creating a new vault, importing your wordlists as new keychains (via the Keychains -> Import menu), and creating new accounts after that to see if your balance reappears?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.