mist 🚀 - Need Assistance - Ethereum Password Not Working

Hi,

to test if your really didn't misspelled your password, launch mist or geth directly. Then attach geth to it, by running:

cd path/to/mist/resources/node/geth
geth.exe attach

When you are in the geth console, you type personal.unlockAccount('account address', 'password') and see if you can unlock it.

If this doesn't work, then you certainly have a wrong password.

frozeman on 18 Jul 2016

@dbfrav I tried to look for code issues in Mist that could create accounts without the user being prompt for a password. I only found these two places - as expected - and added some explanation to them.
Also please make sure to update to 0.8.1 as the error messages were broken in earlier version and always fell back to the - often misleading - "wrong password" alert - regardless of the real error (https://github.com/ethereum/mist/issues/664).

Tl;dr looks good to me, I can't spot any possibility for a data-race, etc resulting in an incorrect account creation, but the code could be refactored though

Please make sure to follow these advices #669.

Code search for "personal.newAccount":

Onboarding-screen: interface/client/templates/popupWindows/onboardingScreen.js#L373-L407

'submit form': function(e, template){  // execute this function when submit is clicked
        var pw = template.find('input.password').value,  // read out first password
            pwRepeat = template.find('input.password-repeat').value;  // read out confirmation password

        if( pw !== pwRepeat) {  // show a warning if they differ 
            GlobalNotification.warning({
                content: TAPi18n.__('mist.popupWindows.requestAccount.errors.passwordMismatch'),
                duration: 3
            });
        } else if (pw && pw.length > 1 && pw.length < 9) {  // show a warning if password is not empty and shorter than 9 characters
            GlobalNotification.warning({
                content: TAPi18n.__('mist.popupWindows.requestAccount.errors.passwordTooShort'),
                duration: 3
            });
        } else if (pw && pw.length >= 9) {  // proceed if not empty and longer than 8 characters
            TemplateVar.set('creatingPassword', true);
            web3.personal.newAccount(pw, function(e, res){  // create new account using the password
                TemplateVar.set(template, 'creatingPassword', false);

                if(!e) {  // update UI if no error during account creation (from node)
                    TemplateVar.setTo('.onboarding-account', 'newAccount', web3.toChecksumAddress(res));
                    TemplateVar.setTo('.onboarding-screen', 'currentActive', 'account');

                    // clear form
                    pw = pwRepeat = null;

                } else {  // show error if connection problem with node
                    GlobalNotification.warning({
                        content: TAPi18n.__('mist.popupWindows.onboarding.errors.nodeNotStartedYet'),
                        duration: 4
                    });
                }
            });
        }
}

Account creation screen: interface/client/templates/popupWindows/requestAccount.js#L23-L63

'submit form': function(e, template){  // execute this function when submit is clicked
        e.preventDefault();
        var pw = template.find('input.password').value;
        var pwRepeat =  template.find('input.password-repeat').value;

        // ask for password repeat
        if(!pwRepeat) {
            TemplateVar.set('password-repeat', true);
            template.$('input.password-repeat').focus();

            // stop here so we dont set the password repeat to false
            return;

        // check passwords
        } else if(pwRepeat === pw) {

            TemplateVar.set('creating', true);
            web3.personal.newAccount(pwRepeat, function(e, res){  // create new account using the password
                if(!e)
                    ipc.send('backendAction_sendToOwner', null, res);
                else
                    ipc.send('backendAction_sendToOwner', e);

                TemplateVar.set(template, 'creating', false);  // update UI
                ipc.send('backendAction_closePopupWindow');
            });

        } else {  // show error if passwords mismatch
            template.$('.password').focus();

            GlobalNotification.warning({
                content: TAPi18n.__('mist.popupWindows.requestAccount.errors.passwordMismatch'),
                duration: 3
            });
        }

        TemplateVar.set('password-repeat', false);  // update UI
        template.find('input.password-repeat').value = '';
        template.find('input.password').value = '';
        pw = pwRepeat = null;
}

luclu on 18 Jul 2016

                                                                                  Hi - Thank you very much for your efforts. I am very new to this. I will try my best to utilize the information you sent and will report back. Thanks again  dbf

dbfrav on 19 Jul 2016

Thank you Frozeman. I was traveling for business the last 24 hours and will apply these suggestions tonight and will report back to announce my findings. Thank you.

dbfrav on 19 Jul 2016

Hello -

Frozeman, I have to say that I am quite unfamiliar with both Geth and Mist, and quite honestly and brand new to Ethereum. I downloaded Ethereum fresh install and promptly afterwards loaded some ether in the wallet after downloading. I really do not know what the two programs "Mist" and Geth" do or really, anything about them. I see I have a file named "Mist" in my Ethereum folder but no file within it to open or launch Mist that I can see. And embarrassingly, I don't know how to open or launch Geth either as there is no launch application anywhere on my computer even when I run search for "Geth".

I want to try the approach you suggest but I need better guidance of what these two programs are, what they do and how to actually open them and launch the window to where you are directing me to type your suggested prompts. I appreciate yours and everyone's patience with me. I am otherwise very tech savvy and a quick learner but being totally brand new to Ethereum/Geth/Mist I am a total "Newbie", so if you work with me a bit I'm confident I can understand and catch on. Am willing to compensate for your help too. Thanks so much!

dbfrav on 19 Jul 2016

@dbfrav there is some quite good documentation on the usage of geth (Mist's bundled default ethereum-client) at http://ethdocs.org/en/latest/account-management.html.

As an alternative I can recommend you to use https://myethereumwallet.com to unlock and transfer your funds. On a side note, this service is hosted directly on github and is running client side in your browser.

luclu on 20 Jul 2016

Luclu - Thank you sir. I really appreciate it, however, as I said above I really need to be helped in understanding the specific step by step actions I need to do with these programs before I can go in and apply your suggestions. Once I'm in https://myethereumwallet.com I do not get the lingo, I don't understand what I'm supposed to do. I need to be guided through this with the understanding that I am brand new and not familiar with these exact steps. If you or anyone could take the time and walk me through these promising remedies, I'm certain I can accomplish. Thank you again.

dbfrav on 20 Jul 2016

OK, so I've read up on Mist and I now better understand what Mist and Geth are. So thank you for the links Luclu. I really want to try what Frozeman suggested above first. However, when I launch Geth, I get the black window that loads up data and there's a blinking white cursor at the base presumably to type some code in? However, when I try to type what Frozeman suggests, nothing I type come out in the window. Nothing is displayed. So I now presume this is not the Console? How do I get to the Geth Console to type a command? This is the instruction I'm trying to follow but cannot find out how to do:

_"In order to create a new account using geth, we must first start geth in console mode (or you can use geth attach to attach a console to an already running instance)"_

I might also add that I contacted Dave at Wallet Recovery Service, just in case I may have made a typo of some sort when creating my password. He has not been able to BrutForce my password so I am more and more convinced that I am using the right password, but when I later created additional accounts through Geth after initial Ethereum Wallet setup, somehow my password has been corrupted. This further makes sense because others have reported this issue and here is a quote referring to this bug on the Accounts Management page which reads :

_“Wrong password” notice. This seems to be a false notice on occasion on current Mist versions. Restart Mist and the problem should go away (if you indeed entered the correct password)._

Restarting did not help me. So again I appeal to anyone for help here. I have a considerable amount of ether coins in this wallet and was willing to pay WalletRecoveryServices a percentage if they were able to succeed in unlocking but apparently they are unable. So I certainly would be willing to offer the same reward to anyone who can help me unlock this account to free up the coins.

dbfrav on 21 Jul 2016

Luclu - I was able to go into myetherwallet and use the JSON keyfile to attempt to unlock but it also asked for a password which when I entered it was also rejected. I'd like also to try Frozeman's suggestion above to verify if there was indeed a typo in my password when I created it but not being so familiar with Geth/Mist I cant find how to open Geth Command Box panel to type the command.

Also, I contacted Wallet Recovery Services to run BruteForce password cracker thinking that I may have typed a typo when I created the original password. Dave at WRS assured me that if I can give him as close to the password as possible, he'd most likely be able to decrypt the wallet. I would have used only one password and I recorded it instantly after creating it. I gave this password to Dave and after 3 days and millions of attempts with variations, he has said it doesn't look good. This suggests to me that somehow, when I created the additional accounts in the Main EtherBase wallet using Geth, that this somehow corrupted, deleted or caused the new account password to supersede the original password yet when we try the newly created account's password, it's also rejected.

TL/dr: I am 100% certain that I'm using the correct password that I used when creating the wallet. There are other users who have reported similar issues with passwords not working. For me, things became corrupted when I created a 2nd account using Geth Cmd Prompt window and creating a password for the new account. I have a sizable amount of ethers in this wallet and am now offering a reward of a healthy percent of them to anyone who can help me unlock it.

dbfrav on 22 Jul 2016

Can anyone take me any further with this?

dbfrav on 25 Jul 2016

You know, I'm quite surprised that besides my own recent posts, this thread has basically gone cold for the past week. I'm surprised that this issue isn't being taken more seriously by others. This is not an isolated issue of a "forgotten password" or a "lost password". I am just one of a number of different people who have had the same or very similar issue with sudden "unrecognized" passwords.

I have never forgotten or lost a password in over 20 years. And especially for an account that holds monetary value, in my case 442 Ethers, I absolutely will know precisely what my password is. I continue to hold and trade bitcoins in a wallet since 2012 and never would be so careless as to "forget" or "misplace" my password. So this is not the sorry circumstance of some careless individual who lost his password and is now crying a storm about it on the forums.

I'd actually be too embarrassed to admit to anyone if I ever actually forgot or misplaced a password for such an important account. No, based on how many other users have shared this same issue, this is a obviously a bug in the Ethereum/Geth/Mist system and each and every one of you should be concerned of why this happens.

All was fine with my Ethereum Basewallet until the day I decided to add an account using the Geth program. Things changed from that moment on. The Geth system asked me to create a password for the secondary account which was done via the Geth Command black window which was a total change-up compared to the steps I took to create the initial Ethereum Base wallet downloaded via Github. So of course, I entered a different password unique to that new account. But immediately after that, my main password did not work. The password I created for the 2nd account, does not work either.

When this initially happened I realized that I wasn't all that familiar with the inner workings of Ethereum, Geth or Mist as I admitted in by my posts above, but I don't think I should have to be an expert with the systems involved just to simply create a wallet, a password and hold and trade my Ethers in the same fashion that I have been doing so with Bitcoin since 2012.

But after the few suggestions offered above last week, I wanted to learn more to show those who were trying to help that I wanted to help myself too, and so over the past week I've studied the system and it's related programs to a degree that I feel I'm much better informed than I was a week ago. I even contacted Wallet Recovery Services to help me with the password just in case of the unlikely chance that I typed a typo when creating the password (which I would have had to do twice because in creating a password you must retype it to insure they match). Dave from WRS assured me that if I just gave him a password that was even CLOSE to the correct password, he'd be able to crack it in minutes. After 4 days he told me it he was having no luck. So, out of desperation, I went further and gave him every password I've ever used in my life online (I have a password keeper) even for accounts I no longer have. None of those worked.

So at this point, I am absolutely convinced that my password was somehow corrupted after creating the additional account in Ethereum Basewallet using Geth. And although some may say "hey, it makes no sense and it's your problem buddy". Perhaps so. I know it makes no sense. But it's factual as I describe. And since this suddenly happened to me with no apparent rhyme of reason, and scouting around this forum you'll see other threads from several others who have had the same or very similar issue, this should concern each and every one of you too because unless we, or someone, can figure out what is happening, and why this is happening, even if it is a rare occurrence, any one of you could be next.

I would like to add that my main interest in solving this issue is not so much in recovering my 442 Ethers, but to correct this "bug" so it doesn't affect other innocent users who trust this wallet with their hard earned coins like I did. So as my thread title now states with a late edit, I am willing to pay 20% of my wallet's contents of 442 Ethers to anyone who can help me help me solve this issue.

I thank all of you who have already offered help above and I thank in advance to anyone else who may be able to shine some light on this.

Holding out hope,
dbf -

dbfrav on 26 Jul 2016

👍2

Dear Mr DBFrav,

First off, I would just like to say I am sorry that you are having such a rough time with this particular issue. Nothing grinds us harder than financial woes, then add technology to this mix.... Yeah I feel ya.

Couple of things I would like to clear up as I didn't see them when i was going through this post.

Exactly which version of Mist / Geth / EtherBase / etc and any applications have you installed that attempt to attach to the local chainstate?

So I know i just asked a lot, so lets break this down. I have ran into this password issue before and it has to do with data being overwritten in the ethereum geth data store.

we need to know what Operating System you are using. (Windows Key + R, type in "msinfo32", go to file\export, then save the text file so it can be email/posted. I prefer zipping it up into a zip file with a password for security.)
Some versions of windows in specific cases may have file history enabled. We may be able to utilize that.
do you back up your computer to an external drive or use cloud backup software?
We need to know what ethereum apps are installed that we may need to remove.
Stop using this PC in Native mode for your Ethereum. Why?
Well its simple really, Any software application that is of high value and is not well suited to fault tolerance, needs a place where it can exist that can be recoverable. That answer to this is Virtualization.
Most computers have enough resources to do this, but many do not. By a copy of windows to use in a Virtualization platform, or rent one on AWS. (Amazon Web Services EC2)

I know how to fool windows into letting me run multiple copies of the chainstate in a singe Native environment, but it is messy and difficult to keep straight, especially when software updates occur and chainstates get ForKED! (Pun intended)

we need a backup of your ethereum folder. Create a backup before modifying anything further.
We may need to do some remote assistance and some data sharing.
We need the password that is used to access the wallet.
we then attempt to rebuild the chainstate with the private keys from your existing installation of geth\etherbase\mist - which may have to be done independently of each other. (This is where this process really gets time consuming.

supere989 on 29 Jul 2016

                                                                                  Hi! I am so grateful for your contact. I am away from home at the present and will be home in the morning, at which time I will comply with all of your requests. You made my night, and I thank you. Looking forward to talking  tomorrow, Best regards, dusty ~

dbfrav on 29 Jul 2016

Also, I thought I would shed some light on why this issue happens. We want options. Because none of us like to have all our eggs in one basket. However, in the software realm of Ethereum, this is bad juju.

As you have already discovered, ethereum applications do not check to see if another ethereum application is installed and will use the same data store in your user profile regardless of what data may already be in there.

This is what I call obfuscated local awareness. And it is a problem in many software applications of this nature. Bitcoin never really had this problem because everyone who forked off the main branch renamed the data store folders for their specific coin. Ethereum apps do not do this.

Okay, so that is why you have this issue. We will see what can be done.

Regards,

supere989 on 29 Jul 2016

@ supere989. All required info forwarded to you. Thanks!

dbfrav on 30 Jul 2016

I am having this exact issue and I know my password is correct. I have a fair amount of ETH that is now locked up. I have come from Coinbase - I don't like their sharing of information.

OSX is El Capitan 10.11.5
Etherium-wallet version: 0.8.1
Geth: 1.4.10

What other info do you need?

shubrich76 on 16 Aug 2016

@ shubrich76 - I still have not resolved my issue. I am still awaiting for help from others.

dbfrav on 16 Aug 2016

I don't know where OSX keeps user files, so if I were you, I'd do a global find on your hard drive for any files that contain the ethereum address of the account you're not having access to. It's possible there may be more than one on your hard drive & the one you believe you're using may not be the one you're actually using. Then using myetherwallet.com, I'd try to unlock each file found using your password (and a blank password, just to be exhaustive). If that still doesn't work, I'd suggest there is indeed a bug that may have caused your keystore file or encrypted private key to become corrupted. If so, definitely use this as a lesson to keep backups & know how to use and recover from them.

(IIRC, command-line geth & the geth embedded into the Ethereum-wallet GUI, at least on Windows, at one time used two different keystore paths. I don't know if they still do.)

destenson on 16 Aug 2016

Hey guys. I have the same problem here: I'm locked out of my ETH on coinbase.
1) It's clean WinX, geth is being used with "--datadir CUSTOM_DIR" (I'd guess its also a part of the ghm... bug?)
2) I have a second account, which was created in console.
3) BOTH passwords I have must be 100% correct (as I have it backed up in TWO independent vaults, And I have entered it manually few times.
EDIT: I have also backups, which I didn't try yest, so we'll see

ursul0 on 25 Aug 2016

well... it was fun, yet still unclear what it was.
I had a password and a backup of the key. BOTH apparently were proper!
Trying accessing my wallet (from here for instance: https://www.myetherwallet.com/#send-transaction) always failed.

1) I've restored old system into VMWare VM - I had Acronis backup of the machine where account was initially created (supposedly before I fuck something up... presumably by moving geth to another drive, removing db...whatever...)
2) for some reason there was no key in (C:\Users\your-user\AppData\Roaming\Ethereum\keystore) so I placed my backup there
3) running "geth account update" and typing my password(that I always thought was the right one) in console allowed me to unlock and change password!
4) inserting the new json into https://www.myetherwallet.com/#send-transaction with a new password just works now....

ursul0 on 15 Sep 2016

👍4

Hi all, I've been having the same issue since I recently updated geth on OSX sierra using terminal commands:

$ brew update
$ brew upgrade
$ brew upgrade ethereum

I also removed the entire blockchain and redownloaded it because of the recent DDOS/synching issues and i've been locked out of my accounts ever since. Although I have 'special characters' like '$'. and '@' in my mist generated password I have used it dozens of times in the past without problems. Password doesn't work on https://www.myetherwallet.com/#send-transaction either.

A possible clue worth mentioning is that i'm getting 'Error: ethereum/ethereum/ethereum 1.4.13 already installed' when I try to update geth to 1.4.14 in my terminal window but according to my latest version GUI clients i'm already running 1.4.14 (Go)!

I will attempt to restore an old backup of my system and run 'geth account update' since it worked for ursul0, however, if I successfully run this command on my old system where exactly will the new json file/s be saved after it's generated? will it simply overwrite the corresponding existing json file/s in the keystore folder or will i need to dig around for it? How does it work?

I have lost access to a four figure sum of ETH but trying to deal with this rationally. Obviously any help, tips or suggestions will be greatly appreciated

kionio on 1 Oct 2016

Hi all, same here - I'm absolutely sure I typed the correct password but it has been changed it obviously right after - hence, a significant amount of ETH is now locked in fact. Is this some sort of fraud pattern and the ETH are being nicked in all affected wallets in some point of time in future?

joniponi on 8 Oct 2016

What a relief.. typed my password out in textedit then pasted into myetherwallet.com. worked first go

kionio on 8 Oct 2016

Did so too ... no success. For a second account without any ETH on it it worked fine ... for the first account with a significant credit not

joniponi on 10 Oct 2016

Sad to see so many others with same issue occurring. I'm still holding hope that someone, somewhere will come forth and help resolve. dbf -

dbfrav on 9 Nov 2016

Bump for hope

dbfrav on 1 Jan 2017

@dbfrav Did you ever get a resolution to this? I am in a similar situation and am 90% confident in the password I thought I used, I've tried a number of hedge cases with no luck either and am getting a little nervous - wondering if you had any breakthroughs?

timlangsford on 13 Mar 2017

I've got exactly the same problem. I remember a little bit the situation: I was installing the Ethereum wallet and the first time I started the wallet it was giving instructions and I could try at the test network or someting. I didn't copy the first wallet address, but I couldn't wait so I created a "new" real account. I can't remember that I filled in a password. After that I thought let's create another wallet (And filled in password) and that worked also, so I decided to use wallet nr.1. I sended 8 eth to it. But now I can't access it anymore....

Ethereummm on 15 Mar 2017

guys, it's some sort of a bug (feature) it happened to me also while I was checking out ubiq(eth clone)..
I fixed it (on windows) few times with the following:
1) open cmd.exe console
2) perform password change "geth account update"
3) do manual input of your password (this is the only place I found that will accept it) and set up a new one

ursul0 on 16 Mar 2017

@226536k - I still have no resolution for this issue.

@ursul0 - Forgive my lack of tech knowledge. Where is cmd.exe console? How do I access this?

dbfrav on 19 Mar 2017

Anyone?

dbfrav on 3 May 2017

I was lucky enough to crack mine with pyth recover.

timlangsford on 3 May 2017

Hi all, I'm in the same boat. Sucks. I certainly have forgotten my priv key.

I'm using this software: https://github.com/lexansoft/ethcracker

Fairly easy to setup, and I've got quite the operation going on now. Cracked my test Ethereum address in like 10 seconds when I set it up for testing.

I now have an combo of passwords to try, only spanning 5h hours. It's done over a million hits now for sure.

I'm so pissed and sad that I forgot my password.

AndyNormore on 24 May 2017

AndyNormore, how are you making out?

dbfrav on 11 Jun 2017

I've learned a lot.

Seems there are FOR SURE bugs with importing pre-sale wallets, and maybe wallets in general.

There's a PreSale tool specifically written for those wallets, you can run a command line and it will tell you if the wallet is valid. Mines valid. You can try the password there, but of course, I've forgotten mine.

I'm now using EthCracker which is nice and easy to setup. I've run about 40 million passwords... and it seems im just getting started. I need to process about 3-10 billion passwords before I find it.

My wallets over at $85,000 USD now. Literally life changing kinda dough. lol

How did you make out?

OH I've also started contacting people who owned my old computers, and hunting them down offering cash to come scan their computer for lost passwords. Hahaaa.

AndyNormore on 11 Jun 2017

@dbfrav - has a solution been found to your issue?

ldrapeau on 11 Jun 2017

@ldrapeau - I have still not found a solution.

dbfrav on 11 Jun 2017

Well hi all, i seem to have the same issue on 2 different computers; Ubuntu and Windows 10.
Mac doesn't seem to have any problems with it. Could this be a bug in the code perhaps encoding, or an added character on creation? Both are running version 0.8.1 i believe and where installed first when they had 0.6.x not sure about "x" here. It's strange that any account i create; i write down a password retest it and it says wrong password. With or without ether in the wallet. Some developers should really really look into this. I noticed i had duplicate key files 2 (unique) without the "UTC" time and 3 With the "UTC" time. Two of those 3 are same as the 2 without. The one that has no duplicate was created in 0.8.1 and the others where created in lower versions.

sworteu on 11 Jun 2017

@dbfrav - If you don't mind (and are willing to be bombarded by a lot of questions - once again - sorry) please drop me a line on my gmail at louis dot fixme.

ldrapeau on 11 Jun 2017

Just email me, [email protected] to start a conversation. I don't mind teaching you this. The more I discuss this and find like minded people, the better OUR odds are to figure this problem out.

AndyNormore on 11 Jun 2017

Hey just an update, I was running EthCracker - but have stopped and need to redo ALL of the breaking in favor of Pythrecover.

Install Python 2, install pip, install... there was one more thing, itll tell you when you try to run. And you're up and running.

I found that the combos are much better to get the EXACT replication of the password I may have used. I recommend it fully.

Note, this is for a PRESALE wallet only.

AndyNormore on 12 Jun 2017

I would like to leave a message publicly that I would not trust ldrapeau with your data.

I had a phone call with him, and he said "Technically, if I unlocked your wallet, I would own the Ethereum". Not a professional thing to say, and certainly does not establish trust. If you're giving some one access to this, there can be no doubt. I have major doubts about this person. Technically, sure, you have access to an account - but that doesn't mean you own the account, or that you have escaped a verbal contract between two parties.

If you agree to a bounty of 20% for password recovery, that's all you get. You are legally bound to return the 80% of the contents.

If you did a file recovery of my vacation photos, and I send you my hard drive - those photos don't suddenly become yours, because you found them.

I'll say it again - do not trust ldrapeau. I suspect he'll take your wallet and run.

I have started https://www.reddit.com/r/ethereumlostpasswords where I will be officially starting a password recovery service that is reputable, trustable, accountable. Contact me there.

I don't know why this is so hard. The sheer greed of people in the password recovery business is incredible. The shadiness is even worse.

AndyNormore on 12 Jun 2017

Dont trust you.

On Mon, Jun 12, 2017 at 10:23 AM, ldrapeau notifications@github.com wrote:

Hi dbfrav,

Sorry, I hope my last post did not scare you, anyway. The next step for me
would be to talk to you over the phone if possible. My name is Louis
Drapeau, I founded Creations Informatiques LD Inc. in 1989, and have been
in computers since then. I'm located in Montreal, Quebec, Canada and can
be reached by phone at 514-355-5666 <(514)%20355-5666>. Regards, Louis

2017-06-11 10:10 GMT-04:00 dbfrav notifications@github.com:

@ldrapeau https://github.com/ldrapeau - I have still not found a
solution.

—
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-307631508,
or mute
the thread
igqqpDX6Dp9WoX8mbH2vLvCEOa2guks5sC_VugaJpZM4JOSdk>
.

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

AndyNormore on 12 Jun 2017

There must have been something in the code that made a password go other than was typed. Not sure what else ever could have happen. For me the file sizes are the same as with versions before, the wallets are unchanged (seen by the modification dates of the files). That means, eighter the newer versions can't read/unlock them or the older versions did not write them the right way. As i've done a transaction with a previous version. That means or points more to be the newer version of "mist" or perhaps "geth" having a read or unlock-problem with older wallets. Perhaps with wallets made in mist 0.8.8 My Wallets where made in 29 december 2016. The same day i downloaded the wallet. Perhaps anyone had the same version?

sworteu on 12 Jun 2017

@AndyNorme - Sorry if my comment translated to something bad to you, I was just trying to explain that whoever unlocks your ketstore adr will technically have access to all the ether in it. This is just pure logic, nothing else. To be more specific, it's clear that the the ether is yours and not mine, I just wanted to bring that fact to your attention, nothing more. Good luck with your project, Louis

ldrapeau on 12 Jun 2017

@sworteu - The key here is to try to reproduce the problem with the (possibly) bugged version. Assuming you can reproduce the problem, I would create an account with the shortest password allowed and then brute force with all combinations which should not take that much CPU, see if the length is preserved or not, that could be a start point. I have not taken the time to read the code for the creation of an account. Trying things is a good way to filter in what exactly is going on.

ldrapeau on 12 Jun 2017

@ldrapeau why would i want to brute force it. It worked before, the key files ar not changed so it must be mist doing something wrong. It's software, where bugs might occour. Let's just try to find the source and don't try to put bandages on everyone with services nobody asks for.

sworteu on 20 Jun 2017

As you wish my freind...

2017-06-20 13:47 GMT-04:00 Dutchhype notifications@github.com:

@ldrapeau https://github.com/ldrapeau why would i want to brute force
it. It worked before, the key files ar not changed so it must be mist doing
something wrong. It's software, where bugs might occour. Let's just try to
find the source and don't try to put bandages on everyone with services
nobody asks for.

—
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-309835461, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ab_igjSyQUwmR6Pq9GOrIbAdcFbfbDmnks5sGAWogaJpZM4JOSdk
.

ldrapeau on 20 Jun 2017

@sworteu - The version wallet I created on was/is 0.8.0.

@AndyNormore - Totally agree with the greed factor. Not so much on this thread but others I've posted on. So many have contacted me and the first question they ask _"How much you willing to pay?"_

Personally, I would help anyone with any problem that I felt I had the skills to match the issue at hand, and my reward would be the feeling of joy I would have in my heart that I was able to help a fellow human being who was in need. I will be contacting you.

dbfrav on 21 Jun 2017

@dbfrav Similar story here. On Februrary 12th 2016, I downloaded and ran Mist 0.3.9 entered my usual password I use for crypto wallets.. Purchased eth via shapeshift and sent it to the wallet.. May 20th I create another account with the same password try to send from the initial and password failed. Second wallet is unlockable. I have since tried new clients with no success. I have been bench marking hashcat and ethcracker tools but they have horrible hash per second rates. Mist wallet encryption is scrypt based and therefore cannot be run on GPU at the moment due to the huge memory requirements. I'm researching a couple of technologies that might help brute force our wallets in realistic time frame. This is definitely a BUG. I've been involved in Bitcoin since 2011 and have never seen the amount of password issues as there are with this garbage mist client. I wish the "founders" would acknowledge that it and perhaps contribute monetarily to develop a scrypt decyrpter platform. There are some technologies out that and also on the horizon that may make scrypt bruteforcing GPUable, like AMD Radeons SSG cards with 1TB mem onboard or microns FPGA boards But its going to take money.

ethtester on 27 Jun 2017

@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 ~

dbfrav on 28 Jun 2017

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.

Neurolicious on 29 Jun 2017

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.

ghost on 3 Jul 2017

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

Thank You!

Raymond Johnson
509-521-8751
[email protected]

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
.

supere989 on 3 Jul 2017

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.[email protected]

ldrapeau on 3 Jul 2017

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
[email protected]

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
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)
.

"

ghost on 3 Jul 2017

do what i did

Neurolicious on 4 Jul 2017

@Neurolicious - How did you open Command Prompt?

dbfrav on 6 Jul 2017

@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"_

dbfrav on 6 Jul 2017

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

Neurolicious on 10 Jul 2017

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.

ghost on 17 Jul 2017

@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.

dbfrav on 17 Jul 2017

@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.

ghost on 17 Jul 2017

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

ursul0 on 19 Jul 2017

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

Neurolicious on 21 Jul 2017

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.

FireAndTheVoid on 31 Jul 2017

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

mdcrews5 on 2 Aug 2017

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

sworteu on 2 Aug 2017

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.

mdcrews5 on 2 Aug 2017

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

sworteu on 2 Aug 2017

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

dbfrav on 6 Aug 2017

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

torbak on 9 Aug 2017

@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

davimac on 9 Aug 2017

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")

frozeman on 9 Aug 2017

@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?

davimac on 9 Aug 2017

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

frozeman on 9 Aug 2017

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!

davimac on 9 Aug 2017

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

frozeman on 9 Aug 2017

@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.

FireAndTheVoid on 9 Aug 2017

@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

davimac on 10 Aug 2017

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

evertonfraga on 14 Aug 2017

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.

acebytes on 24 Aug 2017

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
.

mdcrews5 on 24 Aug 2017

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?

dbfrav on 24 Aug 2017

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
.

mdcrews5 on 24 Aug 2017

😕1

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 on 24 Aug 2017

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

sworteu on 24 Aug 2017

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
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
.

mdcrews5 on 24 Aug 2017

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
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

sworteu on 24 Aug 2017

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 on 25 Aug 2017

👍1

@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.

Freakingcat on 25 Aug 2017

👍2

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)

lkknguyen on 25 Aug 2017

@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 [email protected]).

FireAndTheVoid on 25 Aug 2017

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.

Freakingcat on 25 Aug 2017

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.

lkknguyen on 25 Aug 2017

@lkknguyen Congratulations!

Freakingcat on 25 Aug 2017

❤1 🎉1

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
.

mdcrews5 on 26 Aug 2017

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.

FireAndTheVoid on 26 Aug 2017

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 _

dbfrav on 28 Aug 2017

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
.

mdcrews5 on 28 Aug 2017

@dbfrav CONGRATULATIONS! this is awesome news!!!!! Now you said your password had 7 ADDITIONAL characters prefixed ahead of your password you knew was the correct one? Do you mind telling me the total count of characters in the password and if it included special characters / numbers? Also was this additional 7 character word given to Dave when you initially contacted him? I'm trying to determine if Dave has greatly improved his brute force capability or just reworked what you gave him as possible suggestions..... Thanks and ENJOY your ETH!! I'm so happy for you, we have virtually the same amount of ETH. I hope I can access it again...

ethtester on 28 Aug 2017

THATS AWESOME! Congradulations!

Thank You!

Raymond Johnson
509-521-8751
[email protected]

On Mon, Aug 28, 2017 at 12: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/AF4_MnCl0oAjaNEXkhFHKegjMJdMGHPBks5scmiQgaJpZM4JOSdk
.

supere989 on 28 Aug 2017

@dbfrav Congratulations! As I have also hundreds of ETH locked @FireAndTheVoid is working on a daily basis together to solve my password issue. I also had given Dave twice a try and he was so friendly to run his brute force army, but unfortunately it didnt gain any access. I highly recommend @FireAndTheVoid who is determined not to give up on cracking my password and has written some quite good tools to bruteforce password lists which I made. The lucky day will come. So far tested 3.3 million passwords

Freakingcat on 31 Aug 2017

@ethtester - There were no special characters on the prefix characters of the password and I did not give Dave anything but the 8 numerical digits that I was 100% certain was my password. As I mentioned initially in this post, I have only used several passwords throughout the years (I know, very bad idea) and I have them written down and saved as a text file. The one I used when I created the EtherBase Wallet was my wedding anniversary date in this format: 01234567. Now here's the thing, I hired Dave at Wallet Recovery Services before I created this post. I gave him this password plus, just in case, I gave him all of my passwords. There's no way I would have used anything else but these passwords.

He worked on it for weeks and he finally contacted me saying that after many millions of different combinations, he had no luck so he was pretty convinced that it was a bug in Mist. I never heard from him again until this past Sunday, well over a year later when I woke up, checked my email and was surprised to see a message from Dave. _"Good News!" he said. "I finally cracked your password. The password is (actual numerical digits substituted) "married01234567"._ ...I'm like _"WHAT?? I don't recall adding "married" as a prefix"._ Believe me, I have a very good memory, especially when prompted. This is not something I would have done. But it is what it is. I have to believe I did this because it was, after all, my wedding date. That really got me to thinking of just how fallible our memories can be.

So ironically, FireAndTheVoid and I had just started working together two nights before. We set up some software programs and downloaded Wire.com for secure messaging and then decided to pickup again on Sunday. It was Sunday morning that I got the email from Dave. Talk about coincidence?? Well over a year later Dave comes through.

I asked him if he had been working on it all throughout the past year and he replied:

_"My software is continually evolving and improving, and I sometimes go back and work again on jobs that I feel should be solvable... as yours turned out to be"._

So apparently Dave is always updating his equipment and as this case demonstrates, he doesn't give up.

As I said, no way do I recall coming up with that prefix of "married". Why would I do that when I already knew that was my wedding date? Here's what FireAndTheVoid mentioned to me.

"When you're given this warning: _Make it as strong as if it would protect your house keys!_ We believe the warning to make the password strong scares people into using passwords that they are uncomfortable and unfamiliar with. Then, when the usual passwords don't work, they are surprised they can't get into their account."

After hearing this I thought "Ah yes, I had planned on using my regular password of my wedding date. But after seeing the stiff warning of "Make it as strong as if it would protect your house keys", I can see how I obviously felt the need to strengthen the password, in my case adding the prefix "married" just to make it a little more secure. Problem is, I never wrote that prefix down. I probably thought I'd remember "married" since it was my wedding date. But believe me, I never ever would have believed I wrote that.

So everyone, please consider FireAndTheVoid's suspicion that maybe more of us did this same thing. Hopefully FATV will chime in and explain this more thoroughly. I can't say enough about FATV and of course Dave at Wallet Recovery.
I'll be standing by indefinitely for moral support and you all have my prayers in that you'll all get your wallets unlocked.

God Bless,

dbf -

dbfrav on 31 Aug 2017

🎉1 👍1

Hi guys, I have an offer for anyone who has a password issue on ETH wallet. I had a password issue also (see my nick here in this thread on 3rd July) , so I hired a programmer and we spent days and weeks by tuning up the cracker. Now I have my ETH wallet password back :-) If you need help , I can provide you a finisched functional cracker with added optional functions for a fee to get some invested money back. At first we must consult technical details. So there is an option you dont need to provide me a wallet file at all and I will provide you a finished cracker of course with manual and help. There is no final success reward for me. Otherwise I can provide a different service to crack your password for 15% fee if Im successful. But in the second scenario U have to send me a file. So there are 2 options, to buy a tuned cracker or let me try cracking. For better trust, we can communicate on FB e.g. nevermind. I`m just a happy guy , who has a UTC file password back, but wants to get his invested money for cracking back. Write me on [email protected] or to my acc here.

ghost on 7 Sep 2017

I do understand your frustrations.
Here are a few things you can consider when trying to unlock the account:

Have you had geth installed before Mist (in which case it would have created an ether base at its first start, use the password you used there)
Please also try unlocking via the command line: https://github.com/ethereum/go-ethereum/wiki/Managing-your-accounts
Or the console: $ geth attach (after running a node in an other terminal) -> personal.unlockAccount('0xmyaddress', 'mypassword')
Maybe you used another tool to install geth, back in the day, and this one created an account for you?
The accounts/keys can be found in
Mac: ~/Library/Ethereum/keystore
Win: %APPDATA%\Ethereum\keystore
Linux: ~/.ethereum/keystore

Thats all the help i can give you. This software and the crypto space itself, states clearly that you are responsible for your keys and you need to know how to manage them properly.
Please ALWAYS send small amounts first and try sending out a bit again, before making large money movements!!

This space is ALPHA, and many of the user facing tools, to make all of that convenient and safe need to be build first. We at Mist work on improving the account management - but this is the work off many groups together rather than us only, to ensure the best security we can give.

Many of the issues, don't arise from the software, but the faulty usage over the last two years. Many of the accounts people generated were created a long time ago and with older versions of geth. Maybe you can also try using an old version to unlock the account (again: use the command line here, like stated above)

From my experience in helping people restore their funds, 99% of the case it was a wrong password.

I wish you all the luck, and please try all the above to see if you can finally unlock your funds. Sadly there is not much we can do, as we have no control over your keys, or passwords.

frozeman on 7 Sep 2017

@frozeman: Great post - I agree, may be one other recommendation, for important accounts, I think it's preferable to stick to [A-Z] [0-9] [a-z] characters only (if the software you are using allows it), this will prevent a lot of cases that ended up in here where special characters where used and caused problems. Not to say that special characters would not, work, just a conservative tip to put all chances on your side of not having any issues. Good luck to all, and remember that life is more important than ETH!

ldrapeau on 7 Sep 2017

Hi, thought I would join the conversation here as I have the same issue with regards to the Mist wallet. I have an Etherbase account created in March and quite frankly I do not remember ever setting up a password for it. However, I have a number of passwords that I have written down for crypto related things and absolutely none of these work. This is strange, as like others here I am meticulous about writing down my passwords somewhere.

I have tried using the Geth terminal and have probably tried 50 different passwords thus far. I tried using the python tool which checks all the permutations of possible passwords but am having trouble using it. I fortunately am not missing much on this account (only about 2500 DNT) but it's still worth over $150. I don't know if it is worth sending my info to one of the password crackers as even if they took a 50% fee it wouldn't be much for them.

I do know that I will only be using myetherwallet from now on.

abonn on 13 Sep 2017

Here's a tip in case it helps someone -

I couldn't figure out why my passphrase wasn't working for a long, long time. I eventually downgraded to 0.8.10 and suddenly it worked and I was able to transfer the ETH to a different account.

I'm 100% certain that I was trying the same password in recent versions :-/

m-thomson on 17 Nov 2017

❤2

Thanks for the info. I am not aware we changed anything from that version on in respect to the password input. We will take a look though.

frozeman on 19 Nov 2017

Hi,

I could provide such a tool, but of course you will have to input some
sensitive information from the wallet file. If not I can program a small
computer (raspberry -pi) and send it to you, that way you could run it
without any connection to the internet so you would be sure that nothing
leaks, but the cpu on this small machine is not too strong... Good luck,
Louis

2017-07-03 10:32 GMT-04:00 larandi notifications@github.com:

Hi I appreciate your respond, Im just trying to something on my own, if Im
not successful I`ll come back and ask for a support. A reward 5000USD paid

in ETH is a matter of course.
The problem is I do not want to provide a keystore file file , so a GUI
tool
would be nice. I just try to run python, but I`m not a deep tech guy, so
it
takes some time to me. If you have any other proposal, please come to me.

Stepan.

---------- Původní e-mail ----------
Od: ldrapeau notifications@github.com
Komu: ethereum/mist mist@noreply.github.com
Datum: 3. 7. 2017 15:03:22
Předmět: Re: [ethereum/mist] Need Assistance - Ethereum Password Not
Working
(#982)
"
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 <(514)%20355-5666>
louis.[email protected](mailto:[email protected])

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

"

—
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-312661178, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ab_igkuGRVMaSrB___xT6a1FjHk82NJNks5sKPuSgaJpZM4JOSdk
.

ldrapeau on 30 Nov 2017

Hi I already created my own tool and found the password :-) thank you.
---------- Původní e-mail ----------
Od: ldrapeau notifications@github.com
Komu: ethereum/mist mist@noreply.github.com
Datum: 30. 11. 2017 14:52:39
Předmět: Re: [ethereum/mist] Need Assistance - Ethereum Password Not Working
(#982)
"Hi,

I could provide such a tool, but of course you will have to input some
sensitive information from the wallet file. If not I can program a small
computer (raspberry -pi) and send it to you, that way you could run it
without any connection to the internet so you would be sure that nothing
leaks, but the cpu on this small machine is not too strong... Good luck,
Louis

2017-07-03 10:32 GMT-04:00 larandi notifications@github.com:

Hi I appreciate your respond, Im just trying to something on my own, if Im
not successful I`ll come back and ask for a support. A reward 5000USD paid

in ETH is a matter of course.
The problem is I do not want to provide a keystore file file , so a GUI
tool
would be nice. I just try to run python, but I`m not a deep tech guy, so
it
takes some time to me. If you have any other proposal, please come to me.

Stepan.

---------- Původní e-mail ----------
Od: ldrapeau notifications@github.com
Komu: ethereum/mist mist@noreply.github.com
Datum: 3. 7. 2017 15:03:22
Předmět: Re: [ethereum/mist] Need Assistance - Ethereum Password Not
Working
(#982)
"
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 <(514)%20355-5666>
louis.[email protected](mailto:[email protected])

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

"

—
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-312661178, or
mute
the thread
FjHk82NJNks5sKPuSgaJpZM4JOSdk>
.

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

"

ghost on 30 Nov 2017

Hi, I downgraded to version 0.8 and then changed my password (it kept saying I had the wrong password in the most up-to-date version).

Thank you so much @m-thomson for this tip!

abonn on 30 Nov 2017

@abonn

Hi, did you use 0.8.10 to access your account as well?

pavneet09 on 20 Dec 2017

Hi, no I work with the geth CLI in linux.

ldrapeau on 20 Dec 2017

Yes.

On Wed, Dec 20, 2017 at 12:42 AM, Pavneet Puri notifications@github.com
wrote:

@abonn https://github.com/abonn

Hi, did you use 0.8.10 to access your account as well?

—
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-352920555, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AL7M8HB5Ab4888-Nkj5B_-hbQum2Tgsyks5tCEn-gaJpZM4JOSdk
.

abonn on 20 Dec 2017

Hi everyone, I have the same issue as described by a few people in this thread, I'm 100% certain of my password, but it's not accepted by Geth in cmd or by myetherwallet when I select the keystore. How do I change my version of Geth to 0.8.10 like people are suggesting?

Get Outlook for Androidhttps://aka.ms/ghei36

From: Ev notifications@github.com
Sent: Tuesday, January 9, 2018 8:15:44 PM
To: ethereum/mist
Cc: davimac; Mention
Subject: Re: [ethereum/mist] Need Assistance - Ethereum Password Not Working (#982)

Reopened #982https://github.com/ethereum/mist/issues/982.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/ethereum/mist/issues/982#event-1416809685, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ab4dvVgZz1U93ZEjvGw5uFhGp_5DxMT1ks5tJA9AgaJpZM4JOSdk.

davimac on 10 Jan 2018

@davimac Check https://geth.ethereum.org/downloads/ and click to show older versions.

abonn on 10 Jan 2018

To clarify, I used https://github.com/ethereum/mist/releases/tag/v0.8.10 but that version may have worked for me because it was the version I used to create the wallet in the first place (I can't recall).

But downgrading to whatever version created your wallet is definitely worth a shot. If you can't remember which version it was, then I suggest starting with the above version. At least in my case there was a change introduced after that version that caused my password to no longer work.

Good luck.

m-thomson on 15 Jan 2018

Let me answer here to the "99% forgot their password" comments.
1) Please note that I had two wallets initialised and I had no access only to the coinbase (one of them) the other always worked
2) I have recovered my access to the coinbase wallet by rolling back the image of the entire machine with the node and using my EXISTING key backup and EXISTING password that I always thought was right.

ursul0 on 16 Aug 2018

Good

ali8889 on 18 Aug 2018

@ursul0 it would be very interesting and maybe very helpful for others if you could analyze the two files (two different versions of the keystore/json file) and see what is different.
I think also @holiman could be interested to get a copy of the 2 files (privately and only after there are no funds left on those addresses). Of course you do not need to send the file to the devs for analysis, but it could help others a lot in understanding the problem (again: only send anything after there is no ether left on the accounts and only if you previously confirmed that you are securely/encrypted communicating with the real @holiman ). Otherwise, never send any wallet files around!

philsmd on 19 Aug 2018

@philsmd The JSON file was always the same, just as the password was always correct. What changed is the geth node setup (it was rolled back to the earlier snapshot, no mist wallet was installed at this point... I think)
Also if I remember correctly the unlock still didn't work(the password was not accepted there) but account update did, allowing me to change the password and then all issues were gone

EDIT: probably worth mentioning that password problems appeared sometime after installing mist (was using console before just fine) ...and mist did worked for sometime properly too... Maybe it was mist version update?... The only thing I'm sure of now is that the password suddenly stopped working in mist

ursul0 on 20 Aug 2018

so you are saying that the keystore file remained bit-by-bit identical and only the geth version changed (one older version of geth worked, while all newer versions of geth refused to work)?
Well, it could be still interesting to analyze/see what was the root cause in your case, because in theory also new versions of mist/geth should be compatible with older keystore files. It could be some fixed bug like this: https://github.com/ethereum/go-ethereum/pull/2371 where newline characters were not stripped from the password etc... but I guess even then geth/mist should test both "versions" of the password even in newer versions.
@holiman what do you think? could this case/file be interesting to investigate?

philsmd on 22 Aug 2018

So, there is definitely interesting information, but it's so vague.

So for one thing, I checked out the difference between update versus unlock -- and I couldn't find anything that differs in any essential way (it's the same code paths).
Is it that something stopped working in Geth, or Mist? If the latter, perhaps it always worked in geth? If this is the case, it would be _very_ interesting to know what versions worked/did not work.

So, @ursul0 could you try to write down (to the best of your recollection) the sequence of events that you experienced, if possible with dates (helpful in determining potential bugs/fixes) ? Also, if you do not want to divulge your password, it would (possibly) be useful to know if the password contained anything outside of [a-zA-Z0-9].

I don't think there's any point in analyzing the json files before we have a clearer understanding of the events.

If, however, it indeed was "mist did worked for sometime properly", then it would be VERY interesting to obtain the json file + password and simply go through old versions of Mist and test it.

Mist: Need Assistance - Ethereum Password Not Working

Most helpful comment

All 127 comments

>

>

>

>

>

>

>

Related issues