Skip to content
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.

"Wrong password" label displayed for corrupted account file (win64-0.5) #253

Closed
piotrbednarczyk opened this issue Mar 5, 2016 · 3 comments

Comments

@piotrbednarczyk
Copy link

As I used quite old Ethereum client before, I had to manually change account files in order to import them to Mist. It appeared that during this change i did small mistake - I forgot about comma between address value and "Crypto" label in JSON file. I did not notice it because account is displayed correctly in Mist. But when I tried to send some money from this account I got "Wrong password" message.

I did it on console with geth: geth.exe --unlock account_address
After 3 reties it gave me much more informative message:
Fatal: Unlock account 'xxxxxxx' (xxxxxx) failed: invalid character '"' after object key:value pair

It would be nice to improve feedback in Mist a bit in that case, for example "Corrupted account file" or similar instead of "Wrong password".

@piotrbednarczyk piotrbednarczyk changed the title "Wrong password" label displayed for corrupted account file "Wrong password" label displayed for corrupted account file (win64-0.5) Mar 5, 2016
@luclu
Copy link
Contributor

luclu commented May 19, 2016

Please check if this behaviour still occurs on version 0.7.4 / geth 1.4.4 and report on the outcome!

@luclu
Copy link
Contributor

luclu commented May 21, 2016

I will close this for now, but will stay here to assist you in problems regarding Mist/geth.
Also make sure to try this update of #669:

if you still can't unlock your account try this service: https://www.myetherwallet.com (they implemented a "wallet viewer" following the official wallet-specs; it's client-side; source-code)

@luclu luclu closed this as completed May 21, 2016
@lock
Copy link

lock bot commented Apr 1, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked and limited conversation to collaborators Apr 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants