Need Assistance - Ethereum Password Not Working

[dbfrav]

Greetings -

Forgive me if I've posted in the wrong place. I am a new user of Ethereum and decided to download the EtherBase wallet from Github. After the download I extracted the files and then opened the Ethereum wallet file and it immediately began syncing with the blockchain right out of the box. Once completed it was ready to go and while syncing it did prompt me for a password and I was very careful in typing it twice and recording it to my password book. So once the blockchain synced I loaded some ether into wallet and it credited fine.

Then, the next day I downloaded Geth and Eth-miner and created 2 additional accounts to the main wallet via CMD window prompt and those accounts prompted me to create a password each which I did and recorded those passwords. Next day I wanted to send some ether from the main EtherBase account and I was prompted for the password which I entered. I got error message "wrong password". So I then tried the passwords for each new account that I created in CMD prompt mode but neither worked.

I am very good with passwords. I've never lost a password in my life or even confused them with others. I copy them down immediately when I comprise them so this is not an issue of a "lost password" or a mistyped password as there is a preventative for this in requiring you to retype password when creating the wallet. I am absolutely certain that the password is correct but the EthereumBase main wallet will not recognize it. I'm thinking that adding the two new accounts to the wallet via Geth CMD prompt may have caused this somehow?

I searched and found others who have had the same issue and people reply saying this could be a bug in the system.

As mentioned, in searches I came across several others who have similar issues but I see no remedy and the threads are now old and inactive. Here is a link to someone else having the same issue #161 but no remedy seemed to have taken place and thread was closed so I am hoping someone can help me out. I'd be eternally grateful for any and all assistance.

Best regards,

dbf ~

[dbfrav]

@ethtester: Thanks so much for your story and your efforts. You are much more tech savvy than I on this issue in regards to Mist's inner workings. I've been seeking help from others for nearly a year now with no progress. But the mere fact that people like you continue to report that they have the same password issue certainly indicates a "bug" in the system. There are power in numbers so hopefully with enough of us in unison, we may stir notice from someone who can help us.

User AndyNormore (above) mentioned he started a password recovery service on Reddit dedicated to this Ethereum/Mist problem. I posted there last week to connect with him but he hasn't responded there or here. Hopefully he will or someone else will come along with some guidance.

Let's keep us all updated. God Bless, dusty ~

[Neurolicious]

Hello. I got the same issue about 5 hours ago and finally the password was accepted... open Command Tool and type in " geth account update ACCOUNT_ADDRESS " and then it will ask a passphrase, type in the password you think is 100% right one(you wont see letters when you type it, so dont think that nothing happens). If it fails then do the same thing with another address(create a new one if needed), type the password and if it unlocks the account then change it to same password which is the one on you wish to unlock. When you did that then type " geth account update ACCOUNT_ADDRESS " again with the address you want to unlock, type password again and voila you maybe got it... This shit is bugged as hell and just randomly messing around like that gave me access... Sorry my english is bad but I hope you understand me. I almost gave up myself.

[ghost]

Im having the same issue on the old etherbase account created before hardfork, in the xls file saved password doesnt work for main etherbase account, in contrast to secondary account, where password works. I tried hundreds of possibilities like type it also with caps lock , without numlock, put it twice in a row and also all of my other commonly used passwords, even in combinations, no way. The worst is I know the original password , Im sure it had to be changed by something during time. I tried different PC , nothing works, it always says wrong password on the latest wallet. A functional help will be rewarded of course by ETH coins. ( Brute force password cracker with multi CPU support or etc ) I`m just trying to use python, but it is too slow.

[supere989]

Did you update your account keystore to the latest version of Eth?

Thank You!

Raymond Johnson 509-521-8751 supere989@gmail.com

On Mon, Jul 3, 2017 at 3:50 AM, larandi notifications@github.com wrote:

Im having the same issue on the old accound created before hardfork, in the xls file saved password doesnt work for main etherbase account, in contrast to secondary account, where password works. I tried hundreds of possibilities like type it also with caps lock , without numlock, put it twice in a row and also all of my other commonly used passwords, even in combinations, no way. The worst is I know the original password , Im sure it had to be changed by something during time. I tried different PC , nothing works, it always says wrong password on the latest wallet. A functional help will be rewarded ao course by a lot ofe ETH coins. ( Brute force password cracker with multi CPU support or etc )

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-312614438, or mute the thread https://github.com/notifications/unsubscribe-auth/AF4_Mo4JprU3hY4meTwEOZ0tcl66o2OIks5sKMeRgaJpZM4JOSdk .

[ldrapeau]

Hi,

To all who are having "problems" accessing your things. I can try to help but you have to cooperate, it's that simple, if you don't allow us to ask questions there is not much we can do. Also, it's better to get on a person to person to start, and once a solution is found (or not) you can come back to the forums and share. Good day to all.

Louis Drapeau Creations Informatiques LD Inc. 514-355-5666 louis.fixme@gmail.com

[ghost]

Hi  I just installed tha last wallet and last mist from here, nothing more. Is it all I need ?

https://github.com/ethereum/mist/releases

Thank you.

Stepan,

---------- Původní e-mail ---------- Od: Raymond Johnson notifications@github.com Komu: ethereum/mist mist@noreply.github.com Datum: 3. 7. 2017 14:40:23 Předmět: Re: [ethereum/mist] Need Assistance - Ethereum Password Not Working (#982) "Did you update your account keystore to the latest version of Eth?

Thank You!

Raymond Johnson 509-521-8751 supere989@gmail.com

On Mon, Jul 3, 2017 at 3:50 AM, larandi notifications@github.com wrote:

Im having the same issue on the old accound created before hardfork, in the xls file saved password doesnt work for main etherbase account, in contrast to secondary account, where password works. I tried hundreds of possibilities like type it also with caps lock , without numlock, put it twice in a row and also all of my other commonly used passwords, even in combinations, no way. The worst is I know the original password , Im sure it had to be changed by something during time. I tried different PC , nothing works, it always says wrong password on the latest wallet. A functional help will be rewarded ao course by a lot ofe ETH coins. ( Brute force password cracker with multi CPU support or etc )

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-312614438, or mute the thread https://github.com/notifications/unsubscribe-auth/AF4_Mo4JprU3hY4meTwEOZ0 tcl66o2OIks5sKMeRgaJpZM4JOSdk .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/ethereum/mist/issues/982#issuecomment-312634982), or mute the thread (https://github.com/notifications/unsubscribe-auth/AcdgGmdMxpusItzdj27TVsWjGTcNCV2Jks5sKOEwgaJpZM4JOSdk) .

"

[Neurolicious]

do what i did

[dbfrav]

@Neurolicious - How did you open Command Prompt?

[dbfrav]

@Neurolicious - When I did what you prescribe in Command Prompt, I got the following error message: "geth is not recognized as an internal or external command, operable program or batch file"

[Neurolicious]

You must download GETH then. https://geth.ethereum.org/downloads/

[ghost]

Anyone happen to figure this out? I'm having the same issue. 100% sure I have the correct password (have used it before for sending eth and have it written down), yet I keep getting "wrong password" now.

This happened after I got a new computer and downloaded the ethereum wallet again on the new one.

[dbfrav]

@fort9520 - I started this post exactly one year ago today. You can read through and see the many responses, none of which has helped me though.

One thing is for sure, there's an obvious bug in the Ethereum Wallet system/Geth that I don't think anyone is taking too seriously. I'm not giving up hope though that eventually we'll be enlightened with a fix. Please keep in touch.

[ghost]

@dbfrav. Agreed. This is 100% a bug. I cycled through dozens of passwords in my password manager as a double check with no luck. I was sending ether from this account within the last 30 days as well, so the password clearly worked before.

[ursul0]

To all of you having password issues I suggest to try changing your password like this: "geth account update" do manual typing of your password (this is the only place I found that will accept it) and set up a new one

[Neurolicious]

ursul0 that's what I mentioned above. I got the access to my wallet back using this method.

[FireAndTheVoid]

For anyone here who is not included in the thread https://github.com/ethereum/go-ethereum/issues/2908, here is what I posted there.

I had a similar issue, where I could not unlock my geth account with my carefully recorded password. Luckily, I was able to figure out my issue. Hopefully, this will help some of you. Because my password was so long and because geth doesn't display the characters that are entered, to be on the safe side, I copied and pasted my password when creating the account. Unfortunately, using ctrl+v doesn't work in a Linux terminal. Instead, it set my password to an empty string.

To see if this is the case for you, start up geth in one terminal, then run "geth attach" in another. In the second terminal, try unlocking your account with:

personal.unlockAccount("","")

If it successfully unlocks, it will report "true".

As an alternative, (1) go to myethereumwallet.com > send ether & tokens, (2) load your keystore file, (3) type a space in the password field and then delete it (this will cause the "unlock" button to appear), (4) click unlock.

If you found this helpful, send what you think is appropriate to 0xbcfc16143f7ee5a96aceb736f823ea1747d102bd (ETH only). Side note, this is NOT the account where I had accidentally set the password to an empty string.

[mdcrews5]

Why not just create a "forgot password" option in order to serve the ever growing number of issues this is creating? Just saying......

[sworteu]

You can't. There is no way to recover a password other than guessing it

Op wo 2 aug. 2017 om 19:16 schreef mdcrews5 notifications@github.com

Why not just create a "forgot password" option in order to serve the ever growing number of issues this is creating? Just saying......

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-319738697, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7xq4ewtkzX8OOrL_Ifsu0wSiSOJ5ecks5sUK7-gaJpZM4JOSdk .

-- Met vriendelijke groet, Derk Jochems

[mdcrews5]

Why can't you? It's in the JSON somewhere. I would think this wouldn't be a great decision based on individuals creating contracts, exchanging funds, and executing contracts based around a financial ecosystem. What if one party "forgot" the password. Nothing could be transferred, business is disrupted, people lose money. After reading some of these many threads with this issue, it could also be a "bug" that is corrupting the password. It hasn't been ruled out anyway. I see this is a much larger problem and could potentially push people away from the system. If they goal is bring in more people, and I believe more and more people are beginning to use this platform, we are going to see more and more of this same issue. Simply saying that you "can't" isn't going to be enough for any of these new people. Then....government regulation...I won't even get into that.

[sworteu]

Currently it can't be. It could be made so it can be done but only if a third party would store the recovery thing or yourself. But then, you alread have made a password...

Op wo 2 aug. 2017 om 19:40 schreef mdcrews5 notifications@github.com

Why can't you? It's in the JSON somewhere. I would think this wouldn't be a great decision based on individuals creating contracts, exchanging funds, and executing contracts based around a financial ecosystem. What if one party "forgot" the password. Nothing could be transferred, business is disrupted, people lose money. After reading some of these many threads with this issue, it could also be a "bug" that is corrupting the password. It hasn't been ruled out anyway. I see this is a much larger problem and could potentially push people away from the system. If they goal is bring in more people, and I believe more and more people are beginning to use this platform, we are going to see more and more of this same issue. Simply saying that you "can't" isn't going to be enough for any of these new people. Then....government regulation...I won't even get into that.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-319744985, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7xqw5rbPJVxvvuZFUTyyimsTuxYIuIks5sULSBgaJpZM4JOSdk .

-- Met vriendelijke groet, Derk Jochems

[dbfrav]

@FireAndTheVoid , this didn't work for me either, but thanks for your efforts.

[torbak]

Installed Ethereum Mist for Linux the day 29/04/2017 downloaded from github. In recent years I have never lost a password!! Although I always use the usual passwords. And always save my passwords. None of what I use works. It's frustrating

[davimac]

@dbfrav Hello, I have a similar problem. I know the password is correct, but Geth won't accept it.

Is it possible that....... if you have some malicious software on your computer, then someone could have used a keylogger to steal your password as soon as it was created, then unlocked your account and changed the password? I just created a new account ("geth account new" in the command prompt), then unlocked it immediately using the password I'd just set, to make sure at least that worked. It did, and after unlocking the account, I was then asked to set a new password.

If a hacker did the same thing 12 months ago to you, then maybe that's why your password doesn't work anymore. Sorry to bring this up as a potential cause, as it doesn't lead to a happy ending.

I could be completely wrong though.... looking for some input from the more experienced members out there

[frozeman]

You guys can try using the command line tool to unlock the account. Download/install geth directly, or find it in the Mist data bin folder (Mac: ~/Library/Application Support/Mist/bin/geth, win: %USERDATA%\Mist\bin\geth, linux: ~/.config/Mist/bin/geth).

start it via the command line geth and then in another window geth attach. In the console use: personal.unlockAccount('0xaccountAddress', 'password')

And try so all your passwords an variations.

Additionally you can try using only the terminal: geth --unlock 0xaccountAddress. Then in sth STDIN geth asks your for you password. (Its hard to see between the logs, but it will tell you if you entered correctly with "Account unlocked")

[davimac]

@frozeman I don't use Mist, so that's what I've been trying. I'm certain I know what my password is, Geth just won't accept it. Is it possible my account his been hacked and the password changed?

[frozeman]

I think thats very unlikely, why should anybody make that effort, if he can simply move your funds to his own account?

[davimac]

I guess so they can maintain exclusive access to the account, and drain ETH from it regularly until the unlucky owner realises they've lost access. I don't know, I guess I'm trying to find an explanation to the situation I'm in!

[frozeman]

I can only recommend you what I’ve written above. Please try to use the command line, or alternatively you can import the keystore files to myetherwallet.com. The keystore is in %APPDATA%\Ethereum\keystore

[FireAndTheVoid]

@davimac Changing the password to an account does not render the previous password/keystore file unusable. All "changing" the password does is create a new keystore file for the new password that you created.

When an account is created, a random number is generated that serves as the account's private key. The private key is used to sign transactions that are broadcast to the network. Using an elliptic curve algorithm (see https://en.bitcoin.it/wiki/Elliptic_Curve_Digital_Signature_Algorithm), a public key is generated from the private key. The public key is the account's address. Any transaction that is signed with the private key from a given address can easily be validated by the network as correctly belonging to that address, however it is practically impossible to determine the private key just from the public key.

Using the password, private key, and some other info, the private key is encrypted into the keystore file. The only way to unencrypt the private key is by using the contents of the keystore file along with the provided password.

So, when you change the password to your account, the old password is used to unlock the old keystore file and recover the private key. The recovered private key is immediately encoded using the new password into the new keystore file. Now, with the new keystore file, you can recover the private key using the new password. However, this does not break the old password/old keystore file combination. You could still use them to send transactions over the network.

[davimac]

@FireAndTheVoid thanks for this explanation. I'm at a loss as to why my password doesn't work then! Luckily I didn't have a life changing number of ETH in there, but still looks like I've lost them

[evertonfraga]

Cross-referencing https://github.com/ethereum/mist/issues/2910. Some people used a password cracker to get back their password. Use at own risk.

[acebytes]

I just downloaded the newest version of Mist for the first time about 10 days ago. I have a total of three public addresses in my wallet. I sent a significant amount of tokens to the original address labeled "Etherbase". Unfortunately, my passphrase does not unlock that address, although it easily unlocks the other two addresses in my wallet. That was the only passphrase I was asked to enter during the installation process. I use very secure 64 digit randomly generated passwords. I back them all up, and in addition every text string I generate is added automatically to my clipboard manager history. I've literally tried every single text string in my clipboard (505 entries) and none of them work. Based on what people in this thread have said and based on my own experience losing access to a significant amount of funds, I am definitely inclined to think this is a bug in Mist. I have tried all of the proposed solutions here, and none have worked. I really hope the Mist developers take this issue seriously, instead of assuming that rational people simply forgot or mistyped their passphrase. As it currently stands, I have a six figure USD equivalent of tokens now completely inaccessible. I'm sure I'm not the only one here with serious money on the line. Please, if anyone finds a solution, post your findings here and I will do the same. BTW, I do use symbols in my passwords in addition to numbers and letters. I don't see why this should matter, but I thought it was worth mentioning.

[mdcrews5]

Unfortunately, they treat us as dumbasses and nothing is currently being done....I'm in the same boat friend. Welcome to the club!

On Aug 24, 2017 12:20 PM, "rriot" notifications@github.com wrote:

I just downloaded the newest version of Mist for the first time about 10 days ago. I have a total of three public addresses in my wallet. I sent a significant amount of tokens to the original address labeled "Etherbase". Unfortunately, my passphrase does not unlock that address, although it easily unlocks the other two addresses in my wallet. That was the only passphrase I was asked to enter during the installation process. I use very secure 64 digit randomly generated passwords. I back them all up, and in addition every text string I generate is added automatically to my clipboard manager history. I've literally tried every single text string in my clipboard (505 entries) and none of them work. Based on what people in this thread have said and based on my own experience losing access to a significant amount of funds, I am definitely inclined to think this is a bug in Mist. I have tried all of the proposed solutions here, and none have worked. I really hope the Mist developers take this issue seriously, instead of assuming that rational people simply forgot or mistyped their passphrase. As it currently stands, I have a six figure USD equivalent of tokens now completely inaccessible. I'm sure I'm not the only one here with serious money on the line. Please, if anyone finds a solution, post your findings here and I will do the same. BTW, I do use symbols in my passwords in addition to numbers and letters. I don't see why this should matter, but I thought it was worth mentioning.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324684711, or mute the thread https://github.com/notifications/unsubscribe-auth/AcTYCFiCP2HABnVf_f9nsCw4FcwWedueks5sbaKxgaJpZM4JOSdk .

[dbfrav]

Yes, let us all stay in communication with each other on this and not give up. Here's a question I've not seen asked, how can we contact Mist developers to enlighten them of how many of us have been affected by this bug issue?

[mdcrews5]

Your guess is as good as mine. I don't know if the people who've been responding with advice are actual devs or just people who know more than I. I talked to one guy who acted as if he was a dev and literally told me that users are stupid and there is no bug. We were just a bunch of people who can't remember our password(s).....

On Thu, Aug 24, 2017 at 1:01 PM, dbfrav notifications@github.com wrote:

Yes, let us all stay in communication with each other on this and not give up. Here's a question I've not seen asked, how can we contact Mist developers to enlighten them of how many of us have been affected by this bug issue?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324695615, or mute the thread https://github.com/notifications/unsubscribe-auth/AcTYCDsksOpHJwCCMFA_vsSw8Ldh6mBOks5sbaxlgaJpZM4JOSdk .

[sworteu]

Sorry @rriot we are mostly thinking the same. It seems only no developer is currently doing something about it. Don't try to use any online service to unlock or so. Be patient i'm reviewing the code as is another person to see what's actually happening. It's strange i have the same thing with the "etherbase password". I downloaded mist for the first time in december (12) 2016. So it's probably from a version before that date. Tried Windows, mac and linux versions, no difference. Checked the files, those seem to be ok. So it must be happening on the creation of the Etherbase (or first wallet).

Regards, Sworteu

Op do 24 aug. 2017 om 18:20 schreef rriot notifications@github.com

I just downloaded the newest version of Mist for the first time about 10 days ago. I have a total of three public addresses in my wallet. I sent a significant amount of tokens to the original address labeled "Etherbase". Unfortunately, my passphrase does not unlock that address, although it easily unlocks the other two addresses in my wallet. That was the only passphrase I was asked to enter during the installation process. I use very secure 64 digit randomly generated passwords. I back them all up, and in addition every text string I generate is added automatically to my clipboard manager history. I've literally tried every single text string in my clipboard (505 entries) and none of them work. Based on what people in this thread have said and based on my own experience losing access to a significant amount of funds, I am definitely inclined to think this is a bug in Mist. I have tried all of the proposed solutions here, and none have worked. I really hope the Mist developers take this issue seriously, instead of assuming that rational people simply forgot or mistyped their passphrase. As it currently stands, I have a six figure USD equivalent of tokens now completely inaccessible. I'm sure I'm not the only one here with serious money on the line. Please, if anyone finds a solution, post your findings here and I will do the same. BTW, I do use symbols in my passwords in addition to numbers and letters. I don't see why this should matter, but I thought it was worth mentioning.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324684711, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7xq41Xh9AZGEIjHi_3PSUhyu7_jx1uks5sbaKwgaJpZM4JOSdk .

-- Met vriendelijke groet, Derk Jochems

[sworteu]

Your not dumb. It seems these cases are not handler fair. It's the MOST importat thing to be able to use/unlock your account.

You may help me review the code and find parts where unlocking of the accounts is handled. I'll do my best to find the way to add code or hire a coder to propose a fix.

Don't say how many ether you have. Be helpfull and try to give version information as much as you can. Provide details of what you have done.

I'm not a ethereum developer i'm a Xojo developer but i know c/c++ so i'll do my best to help myself and others.

Currently i'm working with a small team to develop a GUI for Ethereum build on top of Geth. For easier working. Mist seems to be huge and hard to track. Interested in supporting in any way is always welcome.

Op do 24 aug. 2017 om 19:05 schreef mdcrews5 notifications@github.com

Your guess is as good as mine. I don't know if the people who've been responding with advice are actual devs or just people who know more than I. I talked to one guy who acted as if he was a dev and literally told me that users are stupid and there is no bug. We were just a bunch of people who can't remember our password(s).....

On Thu, Aug 24, 2017 at 1:01 PM, dbfrav notifications@github.com wrote:

Yes, let us all stay in communication with each other on this and not give up. Here's a question I've not seen asked, how can we contact Mist developers to enlighten them of how many of us have been affected by this bug issue?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324695615, or mute the thread < https://github.com/notifications/unsubscribe-auth/AcTYCDsksOpHJwCCMFA_vsSw8Ldh6mBOks5sbaxlgaJpZM4JOSdk

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324696604, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7xq9x5U8-kLklWlDQCbRBvT0NotDTgks5sba1GgaJpZM4JOSdk .

-- Met vriendelijke groet, Derk Jochems

[mdcrews5]

I'll help out anyway I can. I had someone tell me it was impossible to recover it, but I don't feel this is true. It's gotta be in there somewhere.

On Thu, Aug 24, 2017 at 1:45 PM, Dutchhype notifications@github.com wrote:

Your not dumb. It seems these cases are not handler fair. It's the MOST importat thing to be able to use/unlock your account.

You may help me review the code and find parts where unlocking of the accounts is handled. I'll do my best to find the way to add code or hire a coder to propose a fix.

Don't say how many ether you have. Be helpfull and try to give version information as much as you can. Provide details of what you have done.

I'm not a ethereum developer i'm a Xojo developer but i know c/c++ so i'll do my best to help myself and others.

Currently i'm working with a small team to develop a GUI for Ethereum build on top of Geth. For easier working. Mist seems to be huge and hard to track. Interested in supporting in any way is always welcome.

Op do 24 aug. 2017 om 19:05 schreef mdcrews5 notifications@github.com

Your guess is as good as mine. I don't know if the people who've been responding with advice are actual devs or just people who know more than I. I talked to one guy who acted as if he was a dev and literally told me that users are stupid and there is no bug. We were just a bunch of people who can't remember our password(s).....

On Thu, Aug 24, 2017 at 1:01 PM, dbfrav notifications@github.com wrote:

Yes, let us all stay in communication with each other on this and not give up. Here's a question I've not seen asked, how can we contact Mist developers to enlighten them of how many of us have been affected by this bug issue?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324695615, or mute the thread < https://github.com/notifications/unsubscribe-auth/AcTYCDsksOpHJwCCMFA_ vsSw8Ldh6mBOks5sbaxlgaJpZM4JOSdk

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324696604, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7xq9x5U8- kLklWlDQCbRBvT0NotDTgks5sba1GgaJpZM4JOSdk

.

-- Met vriendelijke groet, Derk Jochems

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324707024, or mute the thread https://github.com/notifications/unsubscribe-auth/AcTYCAUUfCHWEJSYtn_HI7STllFdEP7Nks5sbbbRgaJpZM4JOSdk .

[sworteu]

I think deeply it's encoding or a simple thing. The wallet files are not corrupted at least in my store, so keep them safe.

Op do 24 aug. 2017 om 19:56 schreef mdcrews5 notifications@github.com

I'll help out anyway I can. I had someone tell me it was impossible to recover it, but I don't feel this is true. It's gotta be in there somewhere.

On Thu, Aug 24, 2017 at 1:45 PM, Dutchhype notifications@github.com wrote:

Your not dumb. It seems these cases are not handler fair. It's the MOST importat thing to be able to use/unlock your account.

You may help me review the code and find parts where unlocking of the accounts is handled. I'll do my best to find the way to add code or hire a coder to propose a fix.

Don't say how many ether you have. Be helpfull and try to give version information as much as you can. Provide details of what you have done.

I'm not a ethereum developer i'm a Xojo developer but i know c/c++ so i'll do my best to help myself and others.

Currently i'm working with a small team to develop a GUI for Ethereum build on top of Geth. For easier working. Mist seems to be huge and hard to track. Interested in supporting in any way is always welcome.

Op do 24 aug. 2017 om 19:05 schreef mdcrews5 notifications@github.com

Your guess is as good as mine. I don't know if the people who've been responding with advice are actual devs or just people who know more than I. I talked to one guy who acted as if he was a dev and literally told me that users are stupid and there is no bug. We were just a bunch of people who can't remember our password(s).....

On Thu, Aug 24, 2017 at 1:01 PM, dbfrav notifications@github.com wrote:

Yes, let us all stay in communication with each other on this and not give up. Here's a question I've not seen asked, how can we contact Mist developers to enlighten them of how many of us have been affected by this bug issue?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/ethereum/mist/issues/982#issuecomment-324695615 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AcTYCDsksOpHJwCCMFA_ vsSw8Ldh6mBOks5sbaxlgaJpZM4JOSdk

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324696604, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7xq9x5U8- kLklWlDQCbRBvT0NotDTgks5sba1GgaJpZM4JOSdk

.

-- Met vriendelijke groet, Derk Jochems

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324707024, or mute the thread < https://github.com/notifications/unsubscribe-auth/AcTYCAUUfCHWEJSYtn_HI7STllFdEP7Nks5sbbbRgaJpZM4JOSdk

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324709852, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7xq95a7afW33Y_WBWtkxTBi8G-MbrIks5sbblSgaJpZM4JOSdk .

-- Met vriendelijke groet, Derk Jochems

[Freakingcat]

Working hard with an expert programmer to get my account unlocked for several months now. It is very frustrating as it becomes more and more clear that there is a bug at Mist which caused the wrong password issue.

[Freakingcat]

@rriot It is very important that you have mentioned that you have used Symbols. My password structure also contained Letters, numbers and symbols. When I worked the last few weeks with my programmer to get closer to the issue, we noticed several potential problems with Mist and symbols. One was that the symbol ^ (Shift 6 on US keyboard) changes after it is typed and Mist just ignores that symbol in the password.

Having run a lot of password variations on a systematic basis and excluded more and more possibilities of human error, it becomes more and more evident that this is a bug in Mist. I ask Mist developers to stop pretending that their Mist wallet code is perfect and so many users are just too stupid and forgot their passwords. I also have a six figure USD amount locked and will not give up trying to get it back.

[lkknguyen]

Has anyone an update to this, my password has special / unicode characters such as +@!=ê (no space) and during the creation process I believe I copy/paste and show/hide password to check. Sent a few coins and now it doesn't work to get out, very frustrating. Need help. Use the same pw for 3 acc, main & 1st do not work, but 3rd does. Let me know if someone found any possible transformation bug during the password creation process. (wallet version 0.8.10)

[FireAndTheVoid]

@lkknguyen While working with @Freakingcat, we found that copying and pasting passwords does not always result in the same characters as if you were to manually type them in. Several symbol unicode characters look alike and your operating system/Mist/other programs can switch between which unicode characters are used, without letting you know. Also, if you have more than just a US English keyboard installed on your computer, you might have undefined behavior. If you (or anyone else) would like, I can help investigate your problem in more depth (my e-mail is fir3andth3void@gmail.com).

[Freakingcat]

I also tweeted this thread to @vitalikbuterin - maybe if a few of us do the same, he might come down from his far distant plane of thinking and realise that ordinary users do have a serious problem because of what looks more and more like a password bug of Mist.

[lkknguyen]

I've just unlocked this, anyone who has their password with ! on MacOS/Mist 0.8.10 (maybe same bug with other), try to write your pass on Mac TextEdit.app and paste to geth client .\geth account update 0x.... and see if it works.

Definitely a bug not on different charsets between MacOS apps e.g TextEdit / terminal Geth or Wallet client. Hope this help.

[Freakingcat]

@lkknguyen Congratulations!

[mdcrews5]

Do we need to be fully synced in Mist for the password to work? I ran geth in cmd window for a week and was never fully synced.

On Thu, Aug 24, 2017 at 11:50 PM, Freakingcat notifications@github.com wrote:

@lkknguyen https://github.com/lkknguyen Congratulations!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-324817119, or mute the thread https://github.com/notifications/unsubscribe-auth/AcTYCMJAZv_BKiyywPOEX68CdlUYWUvtks5sbkSQgaJpZM4JOSdk .

[FireAndTheVoid]

No, you do not need to be synced in order to unlock the account. I know older versions of Mist didn't allow you to even enter the password until after the wallet was synced, but technically, that isn't necessary. With Geth you can definitely unlock while it is syncing. You can also go to myetherwallet.com and try unlocking the account (no sync required). It's a client-side application, so you don't have to worry about your password being sent to them.

[dbfrav]

UPDATE: My wallet has been unlocked! As mentioned way up on the post, I initially hired Wallet Recovery Service over a year ago to brute force the wallet. I gave him what I was certain was my password and he worked on it for weeks and told me that he had run tens of millions of combinations with no luck. So he tended to agree that there was a bug in the wallet software. So month after month I kept checking this post. As time went by the more hope I was losing of ever unlocking my wallet.

Last week I contacted FireAndTheVoid for advice as I saw that he helped others with their wallet password issues and we had our initial conference on Friday. I regained hope. Then, this morning I got an email from Dave at Wallet Recovery Service telling me that he had finally succeeded in unlocking my wallet. I had not heard from him in over a year but Dave finally cracked it, saying he obtained newer and more updated password brute-force software and he went back and worked again on some of the wallets he was unsuccessful with over the past year.

It turns out that my password was indeed what I had remembered it to be, but apparently I had added 7 letters as a prefix to the password that I absolutely do not recall adding. The letters were meaningful and spelled out relation to me so I am convinced that I added them for extra security but never wrote them down with the password which is so unlike me.

FireAndTheVoid is a wonderful fellow who spent some time with me and I thank him for his time as well as all of you for your advice and help to all of us over the past year +. I wish you all eventual success and would absolutely recommend touching base with FireAndTheVoid as he's very knowledgeable and a gentleman. I'd also recommend Dave at Wallet Recovery Service. He doesn't give up and his tenacity eventually paid off for me.

God Bless you all,

dbf _

[mdcrews5]

great to hear!

On Mon, Aug 28, 2017 at 3:13 AM, dbfrav notifications@github.com wrote:

UPDATE: My wallet has been unlocked! As mentioned way up on the post, I initially hired Wallet Recovery Service over a year ago to brute force the wallet. I gave him what I was certain was my password and he worked on it for weeks and told me that he had run tens of millions of combinations with no luck. So he tended to agree that there was a bug in the wallet software. So month after month I kept checking this post. As time went by the more hope I was losing of ever unlocking my wallet.

Last week I contacted FireAndTheVoid for advice as I saw that he helped others with their wallet password issues and we had our initial conference on Friday. I regained hope. Then, this morning I got an email from Dave at Wallet Recovery Service telling me that he had finally succeeded in unlocking my wallet. I had not heard from him in over a year but Dave finally cracked it, saying he obtained newer and more updated password brute-force software and he went back and worked again on some of the wallets he was unsuccessful with over the past year.

It turns out that my password was indeed what I had remembered it to be, but apparently I had added 7 letters as a prefix to the password that I absolutely do not recall adding. The letters were meaningful and spelled out relation to me so I am convinced that I added them for extra security but never wrote them down with the password which is so unlike me.

FireAndTheVoid is a wonderful fellow who spent some time with me and I thank him for his time as well as all of you for your advice and help to all of us over the past year +. I wish you all eventual success and would absolutely recommend touching base with FireAndTheVoid as he's very knowledgeable and a gentleman. I'd also recommend Dave at Wallet Recovery Service. He doesn't give up and his tenacity eventually paid off for me.

God Bless you all,

dbf _

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/982#issuecomment-325277888, or mute the thread https://github.com/notifications/unsubscribe-auth/AcTYCOT9pnC_uCn7X2Bz2l_dhZne9ud0ks5scmiRgaJpZM4JOSdk .