-
-
Notifications
You must be signed in to change notification settings - Fork 650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discourage Private Keys / Keystore #557
Comments
+1 for forcing using to wait 10 seconds when decrypting (while showing a message like the above)—don't show if offline or on localhost / file If you convert to password field, make sure there is an eye icon. We moved away from the password field because even if the very early days people seemed incapable of debugging when they had some extra characters or 0x at the beginning or something. Unlocking existing wallets online and on phishing sites is probably 95% of phishing. It's uncommon someone generates on a phishing site as they typically read guides or tutorials. Not to say we shouldn't encourage doing it offline, just that unlocking is by far the biggest problem. |
Unfortunately these are both textareas, which do not support |
@wbobeirne Any reason not to go with an input? Seems fairly straightforward. |
@wbobeirne I would like to further emphasize MetaMask as a wallet creation option, including to the point of including it in the wallet generation row. We can disable / grey out mnemonic and keystore on web completely. |
@wbobeirne I've updated the issue based on our recent discussion. |
@wbobeirne With Electron dev builds around the corner, and the recent xss vulnerabilities, I'm removing the blocking tag so that we can focus on finally removing raw keys on the web based MyCrypto. |
The text was updated successfully, but these errors were encountered: