Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MultiBit 0.5.15 - "incorrect password" when password is correct #789

Open
nitzany opened this issue May 27, 2017 · 3 comments
Open

MultiBit 0.5.15 - "incorrect password" when password is correct #789

nitzany opened this issue May 27, 2017 · 3 comments

Comments

@nitzany
Copy link

nitzany commented May 27, 2017

I'm using a wallet multibit-20131212202141.wallet with private key file multibit-20131212202141.key.
When trying to send bitcoins i'm requested to enter the "Wallet password", and i receive a message:
"The wallet password is incorrect".

I executed:
openssl enc -d -p -aes-256-cbc -a -in multibit-20131212202141.key -out decoded.key -pass pass:<MY PASSWORD>

the commands exists with status 0.

For some reason which i don't understand the decoded.key is in a binary format:
"decoded.key" may be a binary file. See it anyway?

When i tried with a different private key decoded.key was created in a text format.

Does that say that although the openssl command finished successfully my password might be incorrect?

What should i do so i will have access to my coins?

Thanks.

@nitzany nitzany changed the title MultiBit 0.0.15 - "incorrect password" when password is correct MultiBit 0.5.15 - "incorrect password" when password is correct May 27, 2017
@jonjonez
Copy link

jonjonez commented Jul 2, 2017

Did you open the decoded file using any text editor? Try notepad++

@terry1328
Copy link

Hi, did u solve your problem?

@doge2021
Copy link

https://btc2doge.com/multibit-hd-wallet-seed-words-not-work/
there is bugs in old wallet. check the summary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@nitzany @jonjonez @terry1328 @doge2021 and others