wolovim commented 6 years ago

Description

For many people, creating an Ethereum wallet is the first time they'll be creating an "account" with no password recovery service. Mist and Ethereum Wallet have consistently had issues filed related to users being locked out of accounts. In the Mist UI, this is visible via a "Wrong Password" error notification when attempting to use a given wallet.

Fortunately, many of these issues are resolved by users remembering they had used a different password, or discovering they made a typo in their password, sometimes with the help of a brute force password recovery tool, like pyethrecover.

Unfortunately, still many reports exist with users certain of their password and unable to unlock their wallets. Many of these reports insist that the incident is the result of a bug in the application and we take those claims very seriously. Each of these issues reported have their own nuances as to how they occurred, e.g. moving wallets to another machine, wallet creation during onboarding, specific language keyboards, use of special characters, during Mist version upgrades, and so on. Every one is researched and tried to reproduce.

If you're in this situation, we know you're in a very stressful position and we haven't abandoned you. We do, however, need your help. If a bug exists, our team has been unable to reproduce it yet. If you are able to, it would be of tremendous help to us if you would share the precise steps you took and your relevant system specs (OS, keyboard language, app version number, geth version number).

Specific example links:

special character usage: https://github.com/ethereum/mist/issues/3176#issuecomment-349403728
solved by downgrading Mist version: https://github.com/ethereum/mist/issues/2411#issuecomment-353166968
keystore folder clear resulting in new wallets created: https://github.com/ethereum/mist/issues/3426
pw works on first but not subsequent wallets:
norweigan keyboard use: https://github.com/ethereum/mist/issues/2411#issuecomment-354862699
- electron international keyboard issue: https://github.com/electron/electron/issues/5649
success with pyethrecover: https://github.com/ethereum/mist/issues/3176#issuecomment-347361860

Related issues:

NOTE: please keep this issue substantive and don't comment to say "I'm having this problem too." Use your emojis instead, please :smile:

anormore commented 6 years ago

@evertonfraga Still trying to figure out how to run a script with these characters, one of the mods got back to me, and I'll re-run my scripts with it now:

https://hashcat.net/forum/thread-7181-page-3.html

For all those interested in running their own hashcat instance (@ceric35 )

anormore commented 6 years ago

@evertonfraga Now that I'm learning so much about this problem, I think this image can illustrate how this problem might occur:

If my memory serves me correctly, I did infact use notepad++ to "generate" my password. I very likely copy and pasted it. As you can see the last two characters are line returns, and are 'invisible' to the screen.

So, @evertonfraga proposes that we try cracking/entering the password with these characters. You can achieve this by copy and pasting in the EXACT same way you created it.

This makes me wonder about those guys who created their wallets from the Mac password keeper thing. If they copy and pasted their passwords out of that, I wonder what extra crap also got carried over.

I know this is a real issue in a lot of software (especially with Macs). We run a MySQL + PHP system and work, and people who paste from Mac lose all their formatting and stuff. It wasn't stored in the database properly. So this kind of problem IS very real.

It is my sincere hope this is a step forward to understanding this bug!

anormore commented 6 years ago

Here's another illustration of how your password might get screwed up. In this case I made a password with some extra lines above and below, and added a space.

Oh shit -- it's even possible there's a space on the end of a password!

I've got a pretty sick Hashcat script running now. But none the less, I think I should be able to generate a purposefully "broken Geth account" now by making sure these characters are in my clipboard, generating the wallet, stripping the characters from clipboard, and then trying to open.

This might be able to replicate the problem.

ontheronix commented 6 years ago

Great work so far! I also remember copy/pasting my password into Mist, because I wanted to be sure I wrote it correctly (in the absence of a 'show caracters' option).

anormore commented 6 years ago

I will do some work this evening to see if I can 'break it' and reproduce this bug! From here, it should be rather trivial work to take your password, throw it in to Hashcat, Ethcracker, etc and determine for yourself what the password is.

Stand by for hopefully a really great result -- or nothing at all. I suppose this is how it goes...

From there, I'll try looking at the Mist wallet code to see how they take input variables. From this data we should be able to correlate the problems and come up with a solution in the Mist client itself, maybe.

zeezooPL commented 6 years ago

Same problem here unfortunately. I use same few passwords for most of my accounts.

I created main account with EthereumWallet and I'm sure the password I typed is known to me... I'm not sure which version of EthereumWallet was used but geth that is still on my HDD is in v1.6.6 with geth.exe creation date same as my wallet creation date. Unfortunately personal.unlockAccount in geth 1.6.6 console won't work giving same annoying message "could not decrypt key...". There was ! in my password, so I guess there's a bug somewhere in the code while creating wallets. Tried empty password with no luck. I really hope this will be resolved somehow and few hundred $ that's on my account and few other accounts are not lost :/

It would be really good idea to actually ask for password every single time wallet is accessed... I wouldn't send any ETH to that wallet if I knew something was wrong with password.

evertonfraga commented 6 years ago

For @anormore and those who have a presale wallet:

Parity technologies have just launched a set of tools that can help on that battle. Take a look and see if that helps.

“Tools

In addition to Parity, we provide tools such as ethstore, ethkey, parity-evm. Each of these tools has been improved in various ways. ethstore now supports the brute forcing of pre-sale wallets given a password list for recovery”

http://paritytech.io/velocity-the-fastest-parity-released/ On Fri, 26 Jan 2018 at 20:21 zeezooPL notifications@github.com wrote:

Same problem here unfortunately. I use same few passwords for most of my accounts.

I created main account with EthereumWallet and I'm sure the password I typed is known to me... I'm not sure which version of EthereumWallet was used but geth that is still on my HDD is in v1.6.6 with geth.exe creation date same as my wallet creation date. Unfortunately personal.unlockAccount in geth 1.6.6 console won't work giving same annoying message "could not decrypt key...". There was ! in my password, so I guess there's a bug somewhere in the code while creating wallets. Tried empty password with no luck. I really hope this will be resolved somehow and few hundred $ that's on my account and few other accounts are not lost :/

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ethereum/mist/issues/3513#issuecomment-360920667, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC4BCJbLgq-sMZG-MeDkrr96qw-1rb_ks5tOk_xgaJpZM4RU48I .

ontheronix commented 6 years ago

I personally have created 100 wallets via Geth, and all 100 wallets opened with out a problem.

@anormore @evertonfraga This implies that the error lies at Mist, badly capturing the input? @evertonfraga How many reports has the Ethereum team collected meanwhile? Are there any trends visible?

I have additional information for my report: the addres was generated with geth-windows-amd64-1.6.1-021c3c28 and Mist 0.8.10 (or 0.8.9 in the case that I accidentaly not used the latest version, but the chances are slim)

When I try to boot these old versions, Mist cannot connect to mainnet and shuts down with this error. How can I resolve this?

ceric35 commented 6 years ago

Mine was created using Ethereum-Wallet-linux64-0-7-4. I was not using command line geth at this time.

anormore commented 6 years ago

To reproduce this error, we should be able to take the following text and generate a wallet:

COPY AND PASTE:

Password5%

Notice how here there is a line return beneath Password5% -- make sure you copy it. So it looks like this:

We should then be able to PASTE in to the Geth wallet generation, which would then create a different wallet hash -- if this bug is indeed real.

This makes sense if you later copy and paste Password5% without the line return.

Or perhaps there is another character. Please begin testing this folks.

anormore commented 6 years ago

I am unable to reproduce my theory on MyEtherWallet.com.

I am unable to reproduce this theory with Mist, I was able to copy/paste the text and open a Mist wallet from MEW.

Geth remains untested right now... back later.

anormore commented 6 years ago

OH SNAP I CAN REPRODUCE IT!!!!!!!!!!!!!!!!!!!!!

I created this wallet with the latest version of Mist, 0.9.3.

Let's go through this one more time, with screenshots. My heart is pounding right now ahaaaa.

Create a textfile to store my password with line breaks

New wallet has been generated

Let's check this with MyEtherWallet.com

Let's press UNLOCK WALLET and see if it lets us in

CANNOT LOGIN: I HAVE SUCCESSFULLY SCREWED UP MY PASSWORD!!!! HOORAY!

Let's try to access the wallet by copy and paste from NotePad with the line breaks

IT LET ME LOG

MAJOR VICTORY HERE GUYS! I think. Sorry for all the caps I'm insanely excited now. It does appear that if you have line breaks on your copy and pasted password, or you use some service like the PreSale wallet website from Ethereum.org and rules are not explicitly set to strip that extra stuff off the password - this WILL result in a buggered password!

@evertonfraga Please see if you can repeat these steps and verify I'm not insane.

PS: My donation address if you ever get access to your Eth is: https://etherscan.io/address/0xB5C88ce6CEd344609951eD6409dC35881Fd16996

Because I think I'm still pretty screwed as I probably DID forget my password in addition to this bug. FML.

ontheronix commented 6 years ago

OMG THATS AWESOME!!! So this means Hashcatting with x number of linebreaks to open up your wallet. I'll try the same with Ethcracker and report back! (My hardware is to old for Hashcat)

anormore commented 6 years ago

Just to follow up, when I copy and paste my password from Notepad++ to MEW, this is the visual:

Notice that even MEW has character inputs. And I'm about 95% certain that I generated my password in a notepad file.. but unfortunately I have lost that file. I personally might still be screwed, as I do need to use Hashcat to 'remember' my password combo. This this indicates a massive amount of hope for users who do have a copy and pasted password bug.

anormore commented 6 years ago

Bug: https://github.com/ethereum/mist/issues/3604

I believe this also explains why users suggest this bug 'only takes place when you add funds'. In my bug 3064 I describe that importing a wallet to Mist doesn't ask for a password, or send any type of confirmation that the wallet is imported. I mean, it does show up in the wallet software right infront of your eyes -- but I believe this is why some users perceive this problem the way they do.

It only becomes apparent to the user that their wallet is screwed up when they try to send funds out, because that's the ONLY time Mist asks for a password.

This of course is not the case, as you can see in my report above with password invisible characters are 100% able to completely fuck your wallet up.

sebd-davra commented 6 years ago

Maybe the bug also happens without the special characters but it's hard to reproduce because of the random side of the generation of the wallet.

shopifymatt commented 6 years ago

So correct me if I'm wrong. But, because of a bug with the wallet code, our only recourse is to brute force crack our wallets?

alxlv commented 6 years ago

@shopifymatt Yes

shopifymatt commented 6 years ago

That is a really really shitty situation. I'm still not convinced this is the route cause, I did not copy and paste my password. I genuinely regret using this wallet.

JamesDall commented 6 years ago

@anormore, great work reproducing it for newlines at least!

Am stuck with the same situation, as you can see from my previous posts. Was wondering, does hashcat work with wallets created with Mist? As I read that because it sets the Scrypt N ("n" value in json) to 262144 instead of 1024 of sale wallets and web-wallets, that hashcatting it is impossible due to RAM-limits on video cards?

anormore commented 6 years ago

Hashcat has recently added support for PreSale wallets. There are two types of main wallet types supported.

From Hashcat: https://hashcat.net/wiki/doku.php?id=hashcat 15600 | Ethereum Wallet, PBKDF2-HMAC-SHA256
15700 | Ethereum Wallet, SCRYPT 16300 | Ethereum Wallet, PRESALE -- (You need a new version of Hashcat)

My results with returned characters has failed so far But I will now try to decrypt with Hashcat and my previous example, and then provide the files are reference.

I have a suspicion that there are infact more characters that may be inserted in to the password, thus scrambling the wallet.

anormore commented 6 years ago

I was unable to start Hashcat on my GTX 1080 on a Mist 0.9.3 wallet. I guess the algorithm is indeed changed. I've referenced some guys from those threads here, maybe they'll join us for some support.

Apparently you can still do this on a CPU, but I guess a lot slower. 15kh/s on CPU vs 500 kh/s on GPU -- but hell you're closer than you were. Just slower.

So it does appear newer wallets are going to be a MASSIVE pain in the ass. It also appears pre-sale wallets will be less painful to work with -- however as they went through the staging.Ethereum.org website, we really don't know what extra garbage might have been picked up by their javascript / html form submit / backend systems. We need @evertonfraga for this.

anormore commented 6 years ago

I've attached here some broken files. The password for this wallet is:

Feel free to download the ethereum_v3_broken_wallet.txt and plug it in to www.MyEtherWallet.com

Go ahead and try this password: BrokenTest1!

It should fail.

You will have to download the ethereum_v3_broken_password.txt and copy and paste the entire thing (CTRL + A) ( CTRL + C) and then go paste it. Only then will it work.

ethereum_v3_broken_password.txt

ethereum_v3_broken_wallet.txt

@evertonfraga This is bug is repeatable, check it out.

branmcf commented 6 years ago

@anormore Great work unearthing this bug! I will incorporate your findings into my hashcat/pyethrecover cracking efforts and report back.

tradexy commented 6 years ago

Be interesting to find out the outcome to this apparent bug. @anormore put in some good work here. Would say deserves some ether for bug find.

On 29 Jan 2018 03:51, "Brandon McFarland" notifications@github.com wrote:

@anormore https://github.com/anormore Great work unearthing this bug! I will incorporate your findings into my hashcat/pyethrecover cracking efforts and report back.

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

ontheronix commented 6 years ago

@JamesDall Can you provide your source? Because Hashcat takes the n value as a parameter.

philsmd commented 6 years ago

Hi My reaction to this "finding" is kinda two fold:

the problem with whitespace (in geth/mist) was already mentioned a couple of times on several geth/mist issues. It isn't really a "new" discovery. It's just one more person that was able to reproduced this. It's actually very easy to test if the wallet can be opened with some additional whitespaces. You could just use any password recovery tool that supports this algorithm and feed it with the words + appropriate rules. I'm not convinced that all the users affected by this problem copy-pasted the password with additional special characters (including whitespace). I think many just forgot the password, unfortunately. It's probably too tempting after you found a "password issue" of a software you used and blame it for your problem (instead of blaming yourself first, even if you are not 100% sure that the password is the correct one). I know that there are several exceptions of this, i.e. a lot of users that have a screenshot/text file/password manager entry etc and are indeed 100% sure. Would be interesting to know how many of these affected users copy-pasted the password or used a particular operating system (e.g. macOS or windows).
on the other hand, I do not understand why the devs do not react accordingly (this is not an accusation, I'm just wondering why no obviously required changes are implemented at all). I would be so scared as a dev to hear stories like this, that I couldn't wait a second to implement a user-friendly user-interface change that tries to warn users whenever there are some unprintable characters within the password when the user first set up the password. Maybe even go further and FORCE the user after he/she sets the password, to unlock it at least one time to make sure that the unlocking works after the new wallet was generated etc (also this interface should warn about nonprintable characters, including BOM/carriage return/new lines etc) ... One problem could be that the Mist password form actually never sees the carriage return/line feeds etc... it could be that the replacement already happens at a different layer, e.g. the operating system already does some manipulation and for instance the line feed will already be pasted as a different char into the password form (and it can't really be directly controlled/monitored/identified by Mist).

BTW, I tried to crack the ethereum_v3_broken_password.txt file from anormore (see above) and the password is " BrokenTest1!" (without quotes). i.e. a space at the beginning which is kinda strange (I think the user interface already shows this space though when you check the "Show password" checkbox... you could also copy-paste it again from the form and copy it back to the text editor and you will see a space).

$ JohnTheRipper/run/ethereum2john.py ethereum_v3_broken_wallet.txt > ethereum_v3_broken_wallet.hash

$ hashcat -m 15700 --outfile-format 4 ethereum_v3_broken_wallet.hash dict.txt
2042726f6b656e546573743121

Note: 2042726f6b656e546573743121 is the hex equivalent of " BrokenTest1!" (without quotes, but with a leading space)

Therefore the real discovery that wasn't mentioned yet, is that sometimes (maybe with a particular operating system or operating system version or mist version etc) spaces are inserted instead of the (hidden) control characters (including new lines).

JamesDall commented 6 years ago

@anormore, @ontheronix, this is the article that states that high-n wallets cannot be cracked with hashcat due to memory limitations: https://stealthsploit.com/2018/01/04/ethereum-wallet-cracking-pt-2-gpu-vs-cpu/. If this is true I'll have to get a fleet of AWS machines to do the cracking, which would turn out expensive. Anyone experience hashcatting Mist / high-n wallets?

anormore commented 6 years ago

@philsmd Very interesting that you could use a space instead of the return character....

I just tried as well. You can indeed use a space instead of a return character and it gets added.

I guess I'll try adding a bunch of spaces to my password in Hashcat.

@JamesDall You'll probably want to use EthCracker, in my opinion it's better than Pythrecover. It's pretty good stuff, I did billions of combos with AWS just like you did (PS, Google and Microsoft offer free $300 bucks for new customers ;))

EthCracker recently added "Start at 50%" so you can divide up the workload nicely now.

anormore commented 6 years ago

Really annoyed developers havent responded to this yet. We're sitting here with an identified bug, looking for additional support -- and they're silent.

branmcf commented 6 years ago

FOR THOSE INTERESTED IN GETTING STARTED WITH HASHCAT FOR CRACKING THEIR ETHEREUM WALLET PASSWORD WHILE WE WAIT ON THE DEVS TO APPEAR

Here's what I did to get Hashcat to run on an Amazon EC2 c4.8xlarge instance running Ubuntu 16.04. I don't claim that this is the best way, or even the correct way, to install Hashcat. But it seems to have worked for me.

1) Create an AWS account, log in, configure a c4.8xlarge instance with an Ubuntu 16.04 image, create/download the .pem file, create a security group to allow access via ssh, and spin up the box.

2) Give the .pem file the correct permissions and ssh into the instance (replacing mycert.pem and the instance url with your actual pem file and instance url). $ chmod 400 mycert.pem $ ssh -i mycert.pem ubuntu@ec2-10-200-30-400.us-east-2.compute.amazonaws.com

3) Update apt and install OpenCL $ sudo apt update $ sudo apt upgrade $ sudo apt install ocl-icd-libopencl1 $ sudo apt install opencl-headers $ sudo apt install clinfo $ sudo apt install ocl-icd-opencl-dev $ wget "http://registrationcenter-download.intel.com/akdlm/irc_nas/12513/opencl_runtime_16.1.2_x64_rh_6.4.0.37.tgz" $ sudo apt-get install -y rpm alien libnuma1 $ tar -xvf opencl_runtime_16.1.2_x64_rh_6.4.0.37.tgz $ cd opencl_runtime_16.1.2_x64_rh_6.4.0.37/rpm/ $ fakeroot alien --to-deb opencl-1.2-base-6.4.0.37-1.x86_64.rpm $ fakeroot alien --to-deb opencl-1.2-intel-cpu-6.4.0.37-1.x86_64.rpm $ sudo dpkg -i opencl-1.2-base_6.4.0.37-2_amd64.deb $ sudo dpkg -i opencl-1.2-intel-cpu_6.4.0.37-2_amd64.deb $ sudo touch /etc/ld.so.conf.d/intelOpenCL.conf $ sudo vim /etc/ld.so.conf.d/intelOpenCL.conf paste the following into intelOpenCL.conf and save the file: /opt/intel/opencl-1.2-6.4.0.37/lib64/clinfo $ sudo mkdir -p /etc/OpenCL/vendors $ sudo ln /opt/intel/opencl-1.2-6.4.0.37/etc/intel64.icd /etc/OpenCL/vendors/intel64.icd $ sudo ldconfig $ clinfo $ cd /home/ubuntu $ wget "https://codeload.github.com/hpc12/tools/tar.gz/master" $ tar xzvf master $ cd tools-master $ make $ ./print-devices

4) Clone and build hashcat $ cd /home/ubuntu $ sudo apt install cmake build-essential $ sudo apt install checkinstall git $ git clone https://github.com/hashcat/hashcat.git $ cd hashcat $ git submodule update --init $ make

5) Install screen so you can start a cracking session and return to it later. $ sudo apt-get install openssh-server openssh-client screen $ exit

6) Move the seed file to the remote instance (assuming the seed file is on your desktop). I used ethereum2john.py to create my seed from my backup wallet. $ scp -i ~/Desktop/mycert.pem ~/Desktop/myseed.txt ubuntu@ec2-10-20-30-400.us-east-2.compute.amazonaws.com:~/hashcat

Here are a couple of sources to help you get started actually using hashcat: • https://hashcat.net/wiki/doku.php?id=mask_attack • https://www.4armed.com/blog/perform-mask-attack-hashcat/

Don't forget to spin down your instances when not in use. Good Luck!

evertonfraga commented 6 years ago

@anormore please let's keep this thread constructive.

I know how frustrating this whole process might have been to you and the others. Our joint effort has already resulted in lots of progress around here, including this latest hint on control characters.

This week (and the following) I'll be mostly focused on releasing a Mist+Wallet 0.9.4 version with security and bugfixes, then I'll go back with full attention to this issue, trying to contribute more to the discussion.

In the meantime, I'll be reading and contributing with this issue as time allows.

twigusa commented 6 years ago

Just wanted to add another report that I'm affected by this issue. I have a secure (alphanumeric plus special characters) password which I used for two wallets which were created within minutes of each other. For one, the password works, for the other it does not. The password was copied / pasted in both cases.

It doesn't seem likely that I'll be able to use hashcat or similar to crack it due to the length - I've been lurking and reading this and other associated issues for the past few months and have tried most of the recommendations to no avail. I'm interested to see if there are any developments, glad it's being investigated. Let me know if there's anything I can try / do to help.

sebd-davra commented 6 years ago

@twigusa I am in the same case of you but I created only one wallet with a long password 64 characters alphanumeric.

ceric35 commented 6 years ago

Same case. very long alphanumeric password copy/pasted in mist.

What could go wrong when we copy/paste a password into a mist password field ? Can the content be changed by something else ?

Tguillaro commented 6 years ago

This is what I get everytime I try to send my Eth to another wallet fff

Tguillaro commented 6 years ago

Can anyone help with this?

sebd-davra commented 6 years ago

@Tguillaro try to reinstall the application.

Tguillaro commented 6 years ago

How do I make sure my coins on on there if I delete the wallet and reinstall it

On Thu, Feb 1, 2018 at 4:31 PM, sebd-davra notifications@github.com wrote:

@Tguillaro https://github.com/tguillaro try to reinstall the application.

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

ethtester commented 6 years ago

Hi Guys, I unlocked my Mist "Etherbase" account today after 700+ days of lockout. I installed Mist 0.3.9 back in February of 2016, then after a month or so, shape shifted some BTC into Ethereum to load it up. A few weeks after that I attempted to move a bit of ETH and was prompted for a password which I thought I had never been asked for during installation.

Over the last few months I carefully reviewed my notebooks to get a sense of what was happening and my mindset back in Feb of 2016. I work in IT and keep daily notebooks, with to do lists, contacts, meeting notes and all the many passwords for the systems / environments that I manage. I gathered a list of close to 200 passwords that were self-generated for both work and personal accounts. Alot of these passwords were simple like Bitcoin1000, 2000 , some with with a single special character or an uppercase etc. None of them were complex machine generated passwords and most not longer than 10 characters. With these lists I varied them up a bit and let haschat run at them over several months with no success.

This week I set aside some time to review my notes again and have closer look at the PC that initially held the wallet. Well I fired up file manager and searched for every file created or modified on the date of the UTC wallet file creation. I come across a simple text file labeled ethereum buried on my desktop. Well this file contained the Ethereum password I was searching for so long.... a 14 random character Upper, lowercase letters and one number. This was obviously a password that I had created using some online password tool since like I said, I have always created generally weak passwords myself... Man did I feel stupid but very lucky at the same time. This password would have been next to impossible to bruteforce with hashcat given the current capacities of sram on commericial video cards. Now I was 1000% convinced that I had not been asked or entered a password at the time, looking over my notes, I see that the day I created the wallet was extremely busy for me, so I will assume the prompting and creation of the password was done in "automatic mode" where I was multi-tasking and not fully concentrating on this critical step.

So, that's my dumb story that I will try to never repeat again. I hope and pray all of you will eventually unlock your accounts. I will be keeping a close eye on Scrypt cracking advancements and report them here. I suspect with 10's and possibly 100's of millions dollars locked away in ETH wallets, this will accelerate custom GPU board development. I envision someday a group of locked out ETH users creating an ICO or a go fund me to do just that, but until then, Good Luck to you All.

sebd-davra commented 6 years ago

@Tguillaro dont delete, just reinstall.

Tguillaro commented 6 years ago

Unistalled it and clicked on the wallet to install it and this is what I get

On Thu, Feb 1, 2018 at 7:32 PM, sebd-davra notifications@github.com wrote:

@Tguillaro https://github.com/tguillaro dont delete, just reinstall.

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

Tguillaro commented 6 years ago

123

bvdbos commented 6 years ago

@Tguillaro please create a new issue for this, let's keep this issue on-topic!

Tguillaro commented 6 years ago

I am literally just following the steps you told me to take and telling you the results

On Fri, Feb 2, 2018 at 12:39 AM, Bas van den Bosch <notifications@github.com

wrote:

@Tguillaro https://github.com/tguillaro please create a new issue for this, let's keep this issue on-topic!

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

anormore commented 6 years ago

@Tguillaro We understand that you're having troubles accessing your account, but this is an un-releated issue. The Ethereum wallet for sure has these kinds of troubles for many users, but please start a new issue to get yourself fixed up. Cheers and good luck.

anormore commented 6 years ago

@ethtester Thank you for your story. I went back through all my stuff from that time frame, and I believe your story has jogged my memory! Still going to need Hashcat to crack, but I'm more confident now I remember it. But I think I've tried this particular password before, but it means I for SURE copy and pasted it. Thus, the whitespace bug may still be valid. Setting up for a few days of cracking.

ethtester commented 6 years ago

@anormore In the last few weeks I also researched another option; Hypnosis. I have read that hypnosis for recall has worked for some.. Here are a few names..... Good Luck!

Morpheus Clinic - Toronto http://greenvillehypnotist.com/ Veronica Marimour - Moscow ? Kemila Zsange - Vancouver

anormore commented 6 years ago

Believe me... I'm about to try. Will see what happens at the end of this run.

Tguillaro commented 6 years ago

Forget that issue, I can access it through the old version... I need to know how to get my Eth off this crappy wallet

On Fri, Feb 2, 2018 at 10:54 AM, anormore notifications@github.com wrote:

Believe me... I'm about to try. Will see what happens at the end of this run.

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

ethereum / mist

"Wrong Password" Issues #3513

Description

Specific example links:

Related issues:

COPY AND PASTE:

CANNOT LOGIN: I HAVE SUCCESSFULLY SCREWED UP MY PASSWORD!!!! HOORAY!