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

Ethereum Wallet Password wrong #3244

Closed
JacoBooster opened this issue Nov 4, 2017 · 10 comments
Closed

Ethereum Wallet Password wrong #3244

JacoBooster opened this issue Nov 4, 2017 · 10 comments

Comments

@JacoBooster
Copy link

JacoBooster commented Nov 4, 2017

I have seen a lot of issues with wrong passwords, see #2411 #2610 #2077. From these posts I can conclude that somehow ethereum changes characters of the wallet (especially if you have Apple OSx). I am not very tech savvy, but can someone explain me how this works? I used for example the character @ in my password, how can I see in what characters this is translated?

@korry86
Copy link

korry86 commented Nov 7, 2017

Yep, my password worked great until I sent Ether to my address in Mist. Now, not only does Mist not fully sync, but i can not spend or create a contract because it says my password is wrong. I know its not wrong. Very lame, very very frustrating. Shouldnt happen.. These guys are apparently genuis', yet i haven't had this work properly once. I do not have problems with Bitcoin core, Monero etc... Just stupid Ethereum...

@elpollitodiablo
Copy link

elpollitodiablo commented Dec 5, 2017

I am having this issue, too. I could circle my problem to a special character which I was using in my Password. Do the following:

geth attach
personal.newAccount()

use passphrase FusRoDah
0xAccountA is created (replace 0xAccountA with hash)

personal.newAccount()

use passphrase FußRoDah
0xAccountB is created (replace 0xAccountB with hash)

Run this:

personal.unlockAccount('0xAccountA', 'FusRoDah')
true

and then

personal.unlockAccount('0xAccountA', 'FußRoDah')
Error: could not decrypt key with given passphrase

My setup: Windows 10 64-bit - CMDER (PowerShell produces the same error)

instance: Geth/v1.7.2-stable-1db4ecdc/windows-amd64/go1.9
modules: admin:1.0 debug:1.0 eth:1.0 net:1.0 personal:1.0 rpc:1.0 txpool:1.0 web3:1.0

Mist version 0.9.3 won't let me do any transactions, which lockes my wallet.

EDIT: I forgot: I tried screwing with the encoding of the ß. Things I've tried replacing it with: , ß and nothing/removing it

@anormore
Copy link

Could you try this same process with regular special chars, such as @ ! $ % and so forth?

@sebd-davra
Copy link

sebd-davra commented Jan 6, 2018

I can always reproduce the error with geth in command line :
geth attach
personal.newAccount()
Passphrase:
Repeat passphrase:
I copied pasted the password from notepad++ (64 characters alphanumeric without special characters)
the account is created and the keystore created in the appData keystore folder in windows 10
I am trying to unlock the account with the command
personal.unlockAccount("0xblablablamynewaccount","mylongpasswordalphanum64char")
Error: could not decrypt key with given passphrase

geth version : VERSION: 1.7.2-stable-1db4ecdc
It's clearly an issue with geth to generate and encrypt the keystore.

@wolovim
Copy link
Member

wolovim commented Jan 8, 2018

@sebd-davra I wasn't able to reproduce that on my VM; will double-check on a windows machine when I'm able. Make sure you don't have a copy/paste issue - in your case, see if you can unlock the account with an empty string as the password.

Closing this issue in favor of #3513. If you're able to reproduce any related bug, please help us out by documenting the detailed steps in that issue. Thanks!

@wolovim wolovim closed this as completed Jan 8, 2018
@sebd-davra
Copy link

sebd-davra commented Jan 8, 2018

@marcgarreau I already tried with an empty string before and after, just before, just after my password, with a space only as well and all the combinations of my password 1 to 64 char left to right and right to left.
I reproduced the error 2 days ago and now I cannot :/

@wolovim
Copy link
Member

wolovim commented Jan 8, 2018

@sebd-davra Sorry if I'm misunderstanding you, but what I meant was to check with just an empty string: i.e. personal.unlockAccount("0xblablablamynewaccount", ""). Sounds like you can unlock the testing account already though, so we may have lost that experiment.

@sebd-davra
Copy link

sebd-davra commented Jan 8, 2018

@sebd-davra I already tried personal.unlockAccount("0xblablablamynewaccount", "")
personal.unlockAccount("0xblablablamynewaccount", " ")
personal.unlockAccount("0xblablablamynewaccount", "mylongpassword64charalphanumlowercase ")
personal.unlockAccount("0xblablablamynewaccount", " mylongpassword64charalphanumlowercase")
personal.unlockAccount("0xblablablamynewaccount", " mylongpassword64charalphanumlowercase ")
personal.unlockAccount("0xblablablamynewaccount", "^vmylongpassword64charalphanumlowercase")
personal.unlockAccount("0xblablablamynewaccount", "[a-z1-9]mylongpassword64charalphanumlowercase")
personal.unlockAccount("0xblablablamynewaccount", "mylongpassword64charalphanumlowercase[a-z1-9]")
personal.unlockAccount("0xblablablamynewaccount", "ylongpassword64charalphanumlowercase")
personal.unlockAccount("0xblablablamynewaccount", "^v")

and a lot of permutations as well. always the same response : Error: could not decrypt key with given passphrase :/

@evertonfraga
Copy link
Member

Calling all users that can't access their accounts.
Please help us get more structured information about your "Wrong password" issues.

https://goo.gl/forms/jznmHV6Fpui7Ijds1

@ghost
Copy link

ghost commented Feb 8, 2018

@evertonfraga what shape is the data taking?
Is @JacoBooster statement that apple OSX is a significant factor?

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

No branches or pull requests

7 participants