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

Myst: pwds created on Frozen 0.9.36 not being accepted. #653

Closed
boondogger opened this issue May 18, 2016 · 11 comments
Closed

Myst: pwds created on Frozen 0.9.36 not being accepted. #653

boondogger opened this issue May 18, 2016 · 11 comments

Comments

@boondogger
Copy link

boondogger commented May 18, 2016

This issue is worrysome.

Passwords Created on frozen 0.9.36 not accepted by mist.
Yes they are entered correctly.

passwords used for mining...and worked fine using geth/ubuntu.
several passswords several accounts.

No caps/ No special characters.....some character repetition.
kept pwds simple for quick tweaking.

Node type: geth
OS: ubuntu14.04 frozen 0.6.36 /windows 7/64 (myst)
Network type: main
Mist version: latest

No issues with crowdsale pwd/keystores....worked fine.

help!

@boondogger boondogger changed the title Myst: passwords not being accepted. Myst: passwords created on Frozen not being accepted. May 18, 2016
@boondogger boondogger changed the title Myst: passwords created on Frozen not being accepted. Myst: pwds created on Frozen 0.9.36 not being accepted. May 18, 2016
@luclu
Copy link
Contributor

luclu commented May 18, 2016

@boondogger thanks for reporting, please help me to understand this issue.
Could you please verify that geth 1.4.4 can unlock the account in question?

@boondogger
Copy link
Author

Cannot...
.trying to rebuild system in ubuntu and rebuild  frozen...rrrrr.
Hoping a work around!

-------- Original message --------
From: Luca Zeug notifications@github.com
Date: 18/05/2016 8:58 am (GMT-07:00)
To: ethereum/mist mist@noreply.github.com
Cc: derek 3th3r3um@gmail.com, Mention mention@noreply.github.com
Subject: Re: [ethereum/mist] Myst: pwds created on Frozen 0.9.36 not being
accepted. (#653)

@boondogger thanks for reporting, please help me to understand this issue.

Could you please verify that geth 1.4.4 can unlock the account in question?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@boondogger
Copy link
Author

Not sure where to find geth version...myst file is win64-0-5-1

-------- Original message --------
From: Luca Zeug notifications@github.com
Date: 18/05/2016 8:58 am (GMT-07:00)
To: ethereum/mist mist@noreply.github.com
Cc: derek 3th3r3um@gmail.com, Mention mention@noreply.github.com
Subject: Re: [ethereum/mist] Myst: pwds created on Frozen 0.9.36 not being
accepted. (#653)

@boondogger thanks for reporting, please help me to understand this issue.

Could you please verify that geth 1.4.4 can unlock the account in question?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@luclu
Copy link
Contributor

luclu commented May 18, 2016

@boondogger
Copy link
Author

thanks, you rock!

will try tonight!

On 2016-05-18 11:40 AM, Luca Zeug wrote:

here you go:
|Ethereum-Wallet| https://github.com/ethereum/mist/releases/tag/0.7.4
|geth| https://github.com/ethereum/go-ethereum/releases/tag/v1.4.4
please update both!


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#653 (comment)

@boondogger
Copy link
Author

to clarify.

doesnt myst have latest version of geth prepackaged? or is 1.4.4 a patch?

thanks.

d

On 2016-05-18 11:40 AM, Luca Zeug wrote:

here you go:
|Ethereum-Wallet| https://github.com/ethereum/mist/releases/tag/0.7.4
|geth| https://github.com/ethereum/go-ethereum/releases/tag/v1.4.4
please update both!


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#653 (comment)

@luclu
Copy link
Contributor

luclu commented May 18, 2016

Mist - currently only cointaining one DApp "Ethereum-Wallet" - thus Ethereum-Wallet, is bundled with geth. Version 0.7.4 comes with geth 1.4.4.

Please try out the wallet. If this is not working try geth standalone. On terminal run geth --unlock <account>.

@luclu
Copy link
Contributor

luclu commented May 19, 2016

Also please have a look at this and report back here! #669

@luclu
Copy link
Contributor

luclu commented May 21, 2016

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

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

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

Hey luca.

still no luck.

The accounts were generated in first week of august last year on the
frozen geth release, ubuntu14.04

Is it possible the keystores may have been altered?

5 accounts have balances

all accounts have same password.

I loaded geth 09.36 and tried to unlock accounts using all three of my
standard passwords (geth wouldnt sync) but i would get mac errors
indicating pwd decrypt issue.

i used

for ( var i = 0; i < eth.accounts.length; i++ ) try { personal.unlockAccount(eth.accounts[i], "password"); console.log("unlocked " + eth.accounts[i]); } catch (err) { console.error("Unable to unlock account: " + eth.accounts[i] + " " + err); }

to cycle accounts through individual passwords, and get MAC error at
each iteration.

the keystores were generated on an ubuntu machine, copied to usb in aug,
then eventually transfered to windows 7 machine.

is it possible that windows would change the keystore files in any way?

Is the filename required to be not changed? ( i added act balance to
keystore file name)

would you be able to look at one and tell me if is corrupt?

thanks,

dumbfounded.

(password was written down so something doesnt jive)

On 2016-05-21 5:02 AM, Luca Zeug wrote:

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

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


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#653 (comment)

@lock
Copy link

lock bot commented Apr 1, 2018

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

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

No branches or pull requests

2 participants