Skip to content
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

No warning if wallet is not protected with password upon creation #2143

Open
leafcutterant opened this issue Feb 2, 2017 · 1 comment
Open
Labels
enhancement ✨ security 🔐 technical issue that affects security of funds

Comments

@leafcutterant
Copy link

2.7.18, Windows standalone version

I was playing around with wallet creation and was surprised that leaving the password boxes empty, I could pass the password-setting screen without any warnings.

Storing seeds and xprv's unencrypted is not a good idea and could do much harm to the unwary novice user. How about making this opt-out? Like, when it's not a watch-only wallet, letting the user though only after ticking a box in a pop-up message that "I've understood the risks" and pressing "OK, proceed unprotected".

@AbdussamadA
Copy link
Contributor

AbdussamadA commented Mar 10, 2017

Actually often what happens is that people forget their passwords and lose their bitcoins that way. People getting hacked is much more rare occurrence. Besides the thinking goes that if someone has access to your computer then they can just install a key logger and get your password that way. Even bitcoin core doesn't ask you to set a password by default for these reasons.

@bauerj bauerj added enhancement ✨ security 🔐 technical issue that affects security of funds labels Jan 16, 2018
Toporin pushed a commit to Toporin/electrum-satochip that referenced this issue Aug 10, 2021
Zbar: Update to git master to fix build with autoconf 2.70
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ security 🔐 technical issue that affects security of funds
Projects
None yet
Development

No branches or pull requests

3 participants